Repository navigation
ci: bump python-bandit-scan to v1.0.2 - #458
Conversation
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Dependency ReviewThe following issues were found:
License Issues.github/workflows/bandit.yml
OpenSSF Scorecard
Scanned Files
|
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues were identified for the Bandit action version and commit-SHA update.
No open issues 🎉
What changed in this PR
Updates the Bandit security-scanning action to v1.0.2 to support the repository’s upcoming SHA-pinning requirement, addressing #457.
Changes:
- Bumps
DevSecNinja/python-bandit-scanfrom v1.0.1 to v1.0.2 using a full commit SHA. The release pins its nested actions; existing workflow inputs remain unchanged.
| File | Description |
|---|---|
.github/workflows/bandit.yml |
Updates the Bandit action’s pinned commit and version comment. |
Review effort: Balanced
Bumps
DevSecNinja/python-bandit-scanfrom v1.0.1 to v1.0.2 (60a892a79e752ff1b425c6ebac2543a50b06fc6d). The release pins the two actions the composite action runs (actions/upload-artifact,github/codeql-action/upload-sarif) to full-length commit SHAs. Without this, the Bandit job fails once the repo requires SHA-pinned actions (DevSecNinja/repo-steward#136).Other changes in v1.0.2: optional
artifact_nameandartifact_overwriteinputs (the defaults keep today's behaviour), Bandit installed with TOML support, andconfig_pathpassed as one quoted argument.The commit was made by repo-steward (
steward commit-files) and is signed by GitHub.Closes #457
Summary by CodeRabbit