add machine-readable vuln scanner execution evidence - #968
Merged
aaronjmars merged 3 commits intoAug 26, 2026
Conversation
Contributor
Author
|
Runtime follow-up (2026-08-26): the execution-evidence instrumentation was exercised in real Actions runs.
This is why the provisional dependency claims remain unpromoted: the report is not treated as scanner-verified without an invocation record. |
- rm -f the wrapper path before the heredoc so a pip-installed scanner's symlink (e.g. semgrep/slither) can't be followed and recreated in the global bin dir; always writes a plain file into /tmp/bin. - Move "Verify vuln-scanner execution evidence" below "Upload egress audit log" so the "Egress hardening P2" comment documents the step it precedes. Co-Authored-By: Svector-anu <svector@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
why
A vuln-scanner run can stage Semgrep, TruffleHog, OSV-Scanner, Slither, and cargo-fuzz successfully while the harness report says they were skipped. Model prose cannot prove whether a scanner actually ran.
fix
This keeps the existing best-effort behavior and does not turn an absent optional scanner into a workflow failure.
verification
git diff --checkpassedscripts/stage-vuln-scanner.shand.github/workflows/aeon.yml32931159345demonstrated the evidence gap: staging succeeded, but the agent report claimed all scanners were skipped