Skip to content

Scan Cargo.lock with OSV-Scanner - #202

Merged
jadamcrain merged 1 commit into
mainfrom
osv-scanner
Oct 9, 2026
Merged

jadamcrain merged 1 commit into
mainfrom
osv-scanner

Conversation

@jadamcrain

Copy link
Copy Markdown
Member

Makes the security workflow symmetric with dnp3's (stepfunc/dnp3#451).

cargo audit only reads the RustSec database, so an advisory a crate maintainer publishes only as a GitHub security advisory goes unnoticed (dnp3 had one: GHSA-6g2r-675j-hx59 in xxhash-rust, not in RustSec). The new osv-scanner job scans Cargo.lock against OSV, which covers both.

The job is identical to dnp3's: same triggers as the cargo audit job, verdict taken from the JSON report, a run without a valid report reported as a tool failure rather than a finding, report uploaded, image pinned by digest (ghcr.io/google/osv-scanner:v2.6.0). The only difference is actions/checkout@v7, matching the rest of this workflow.

Locally, OSV-Scanner finds no vulnerabilities in rodbus's current Cargo.lock (198 packages).

cargo-audit only reads the RustSec database, so advisories that crate
maintainers publish as GitHub security advisories can go unnoticed. OSV
covers both. Same job as dnp3's security workflow (stepfunc/dnp3#451).
@jadamcrain
jadamcrain merged commit c485fcd into main Oct 9, 2026
31 checks passed
@jadamcrain
jadamcrain deleted the osv-scanner branch October 12, 2026 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant