-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Add pre-commit detection for malicious unicode chars #51050
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pre-commit detection for malicious unicode chars #51050
Conversation
| files: ^\.github/workflows/.*$|^\.github/actions/.*$ | ||
| require_serial: true | ||
| entry: zizmor | ||
| - repo: https://github.com/lirantal/anti-trojan-source |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like no activity on this repo since last 3 years. not sure are they are maintaining it or not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. Was just picking the first I could find.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As further discussed in https://apache-airflow.slack.com/archives/C015SLQF059/p1748180085592359 --- maybe we rather roll-our own as the list to cover is way larger than the pre-commit I proposed here.
|
At least ' char FF07 FULLWIDTH APOSTROPHE was not taken seroious by the pre-commit. |
|
Closing as not needed. |
Wake-up call after reading https://daniel.haxx.se/blog/2025/05/16/detecting-malicious-unicode/
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.