You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This runs both bandit and pip-audit with sensible defaults: blocks the job on HIGH-severity code issues and on dependency vulnerabilities that have a fix available.
@@ -85,7 +85,7 @@ This runs both bandit and pip-audit with sensible defaults: blocks the job on HI
@@ -172,15 +172,15 @@ The job fails (non-zero exit) when **either** tool finds issues above its config
172
172
173
173
## Outputs
174
174
175
-
- **PR comment** — created on first run, updated in place on every subsequent run (keyed on a hidden `<!-- security-scan-results -->` marker).
175
+
- **PR comment** — created on first run, updated in place on every subsequent run. The comment is keyed on a hidden `<!-- security-scan-results::{workflow-name} -->` marker, so multiple workflows on the same PR each maintain their own separate comment.
176
176
- **Step summary** — the same report is written to the workflow run summary, visible under the "Summary" tab.
177
177
- **Artifact** — `pip-audit-report.json` and `results.sarif` uploaded under the name set by `artifact_name` (default: `security-audit-reports`) for download or downstream steps.
178
178
- **Exit code** — non-zero when blocking issues are found, so the job fails and branch protections can enforce it.
0 commit comments