-
Notifications
You must be signed in to change notification settings - Fork 15
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
feat(zizmor): add a reusable workflow for zizmor GitHub Actions static analysis #605
base: main
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
2f972d2
to
9488aad
Compare
…c analysis This is a [reusable workflow] which runs the [`zizmor`][zizmor] static analysis tool on a repo's GitHub Actions workflow files. This will report things such as whether there is potential for untrusted code to be injected via a template. See a full list of checks in [the documentation][zizmor-checks]. This workflow will run zizmor, upload results to GitHub's code scanning service (requires an Advanced Security subscription for private repositories), and comment on the pull request with the results. The comment will be re-posted on each run - and previous comments hidden - so the most recent comment will always show the current results. [reusable workflow]: https://docs.github.com/en/actions/using-workflows/reusing-workflows [zizmor]: https://woodruffw.github.io/zizmor/ [zizmor-checks]: https://woodruffw.github.io/zizmor/audits/
9488aad
to
94890b3
Compare
This comment has been minimized.
This comment has been minimized.
In this PR I introduced and fixed some problems that the script found. You can see that above 👍 If you look at the files changed tab, you can see results for the other files (same as in the comment) |
😢 zizmor failed with exit code 14. Expand for full output
|
I decided to leave this for the time being, because I don't want us to "randomly" add shared workflows for different tools and rely on repository owners to pick the ones they like. We as an organisation should have a position on this. |
This is a reusable workflow which runs the
zizmor
static analysis tool on a repo's GitHub Actions workflow files. This will report things such as whether there is potential for untrusted code to be injected via a template. See a full list of checks in the documentation.This workflow will run zizmor, upload results to GitHub's code scanning service (requires an Advanced Security subscription for private repositories), and comment on the pull request with the results. The comment will be re-posted on each run - and previous comments hidden - so the most recent comment will always show the current results.