Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ci: fix lint permissions + add Trivy image scan + pip cache #42
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
Uh oh!
There was an error while loading. Please reload this page.
ci: fix lint permissions + add Trivy image scan + pip cache #42
Changes from all commits
5218b16File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
When this workflow runs in a private/internal repository, the
Upload Trivy resultsstep can fail becausegithub/codeql-action/upload-sarifrequiresactions: readin addition tosecurity-events: write; GitHub's SARIF upload docs mark that permission as "only required for workflows in private repositories". Since this job-levelpermissionsblock sets unspecified scopes tonone, addactions: readhere.Useful? React with 👍 / 👎.
Check warning on line 97 in .github/workflows/ci.yml
.github/workflows/ci.yml#L97
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.
🛑 Logic Error: Downgrading from v4 to v3 loses security patches and features from the newer version. This appears to be an unintended regression, especially since other actions are being upgraded (build-push-action v5→v6).
Restore to v4 or provide justification for the downgrade.
Check warning on line 100 in .github/workflows/ci.yml
.github/workflows/ci.yml#L100
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.
🛑 Logic Error: Downgrading from v4 to v3 loses security patches and features. This regression contradicts the PR's goal of improving security.
Restore to v4 to maintain current security posture.
Check warning on line 108 in .github/workflows/ci.yml
.github/workflows/ci.yml#L108
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.
🛑 Logic Error: Downgrading from v6 to v5 loses recent security patches and improvements while simultaneously upgrading build-push-action to v6. This version inconsistency creates an incoherent dependency state.
Restore to v6 for consistent versioning and security fixes.
Check warning on line 128 in .github/workflows/ci.yml
.github/workflows/ci.yml#L128
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.
🛑 Security Vulnerability: Using
@mastercreates a critical security and stability risk. The workflow will pull unverified code on every run, potentially introducing breaking changes, malicious code, or untested features.Pin to a specific SHA or version tag for security and reproducibility.
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.
When two pushes to
mainare processed concurrently, another run can retaglatestbetween this job's build/push and this scan. The SARIF upload is then attached to the current commit while describing a different image, so alerts can be missed or misattributed; scansteps.build.outputs.digestor the SHA tag instead of the mutablelatesttag.Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.