Skip to content

Task: add a RustSec advisory scan to CI (audit Medium) #29

Closed

Description

@tonibergholm

Part of #24

Question

CI runs fmt/clippy/tests/docs/CodeQL/Dependabot but no lockfile advisory scan (audit Medium). Add one — cargo audit or cargo-deny — to .github/workflows/ci.yml, with pinned advisory-database update behavior. Executed in-map per the map's Notes override (AFK task): resolve with what landed (tool chosen, job wiring, pinning policy) and any facts later tickets depend on.

Activity

  1. self-assigned this
    on Jul 10, 2026
  2. tonibergholm commented on Jul 10, 2026

    @tonibergholm
    MemberAuthor

    Resolution

    Executed (the map's one sanctioned in-map execution item). The scan is wired and proven green: PR #37 (awaiting merge), whose own checks exercised the new job — cargo audit (RustSec advisories): pass alongside the existing matrix.

    What landed:

    • Tool: cargo audit via rustsec/audit-check@v2 — the RustSec org's own action, pinned by major tag consistent with the repo's other actions. Chosen over cargo-deny because the audit finding asks for advisory scanning only; deny's license/ban/source checks are separate policy surfaces nobody has asked for.
    • Wiring: a separate .github/workflows/audit.yml (the codeql.yml pattern), not a job in ci.yml as the ticket sketched — the scan needs a daily cron (23 6 * * *) so newly published advisories surface without any code change, plus Cargo.toml/Cargo.lock/workflow path filters and workflow_dispatch, none of which fit the test-matrix workflow. Permissions: contents: read, checks: write.
    • Pinning policy: the action is pinned @v2; the advisory database is deliberately unpinned (fetched live each run) — that live fetch is the mechanism by which the daily run flags new advisories against an unchanged lockfile.
    • Posture: vulnerabilities fail the job; informational advisories (unmaintained/unsound) warn without failing.

    Facts later tickets may depend on:

    • Today's lockfile (247 crates) scans clean of vulnerabilities. One informational warning exists and is expected in the daily output: RUSTSEC-2026-0173 — proc-macro-error2 2.0.1 is unmaintained, reachable only via defmt-macros (a target-gated transitive dep; cargo tree -i finds no host-platform path to it).
    • A future genuine advisory will fail the daily scheduled run — triage lands on whoever watches CI, per the triage-labels flow.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

wayfinder:taskWayfinder ticket: manual work unblocking a decision

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions