feat(ci): add osv-scanner to the dependency audit, merge into one dashboard #248
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!248
Loading…
Reference in a new issue
No description provided.
Delete branch "osv-scanner"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements recommendations 1, 4 and 5 from the scanner review.
1. OSV-Scanner next to
pnpm auditdependency-audit.ymlinstalls OSV-Scanner v2.6.0 from the GitHub release, pinned by version and SHA-256. It does not use thealxndr42/osv-scannerreusable workflow: that is a single-maintainer repo, and it fails the run on any finding.pnpm-lock.yaml, so it also finds transitive packages. Its database is OSV.dev, the same one Renovate uses.pnpm audit.4. One merged dashboard
found by: …. The headline showsFindings per scanner: pnpm audit: N · osv-scanner: M.5. SARIF artifact
osv.sarifis uploaded with thedependency-auditartifact. Nothing reads it yet. It is there for a Forgejo security tab (forgejo/forgejo#3669), if one is built.Tested locally with real output from both scanners on the current lockfile. Both find the same 6 advisories, the merged list has 6 checkboxes, and a ticked box stays ticked.
Not tested in CI: CI does not run this workflow (it runs only on schedule or by hand). After the merge, start
dependency-audit.ymlby hand to check it.Follow-up: compare the two scanners for 2 to 4 weeks, then remove the one that finds less.
🤖 Generated with Claude Code