Dgwarlug47 patch 1

[dgwarlug47]

Please follow the guide below

• You will be asked some questions, please read them carefully and answer honestly
• Put an x into all the boxes [ ] relevant to your pull request (like that [x])
• Use Preview tab to see how your pull request will actually look like

---

Before submitting a pull request make sure you have:

• Searched the bugtracker for similar pull requests
• Read adding new extractor tutorial
• Read youtube-dl coding conventions and adjusted the code to meet them
• Covered the code with tests (note that PRs without tests will be REJECTED)
• Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

• I am the original author of this code and I am willing to release it under Unlicense
• I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

• Bug fix
• Improvement
• New extractor
• New feature

---

Description of your pull request and other information

Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.

[dirkf]

How is this going to differ from flake8 linter already in workflows?

Feel free to explain this by completing the PR template properly.

[github-advanced-security]

You have successfully added a new CodeQL configuration /language:python. As part of the setup process, we have scanned this repository and found 23 existing alerts. Please check the repository Security tab to see all alerts.

[dirkf]

The results of the test run don't offer anything much. The diagnostics highlight these features:

• "Inefficient regular expressions" which have never been a problem but might be adjusted in future if anyone cares
• "Incomplete URL substring sanitization": a deliberate code pattern that has no security impact in yt-dl (not that anything much does)
• "Default version of SSL/TLS may be insecure": invoked only on old Python versions that don't support more recent security protocols
• "Use of insecure SSL/TLS version": ditto
• "Use of a broken or weak cryptographic hashing algorithm on sensitive data": matching what's done by a target website, or locally with no security impact.

If the PR is correctly completed we could have this as an optional workflow to run every so often but it's not suitable to be incorporated into the build or test processes.

[dirkf]

Supserseded by #32745.