Skip to content

[Infra] Supply-chain hardening (cargo audit / cargo deny + Dependabot) #31

Description

@Gbangbolaoluwagbemiga

Problem

There is no automated scanning for known-vulnerable dependencies in either the cargo or npm trees,
and no automated dependency updates.

What needs to be done

  • Add cargo audit (RustSec advisory DB) as a CI step; fail on vulnerabilities
  • Add cargo deny with a deny.toml covering advisories, licenses, and duplicate/banned crates
  • Add .github/dependabot.yml for cargo, npm (root + backend/), and github-actions
  • Triage and resolve the first batch of findings

Acceptance criteria

  • CI fails on a known-vulnerable dependency
  • deny.toml committed and passing
  • Dependabot opens update PRs

Relevant files

.github/workflows/node.yml, new deny.toml, new .github/dependabot.yml, Cargo.lock, package-lock.json, backend/package-lock.json

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    infraCI/CD, builds, toolingsecuritySecurity-sensitive work

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions