Skip to content

Add a cargo-deny supply-chain gate to CI (advisories, licenses, bans) #94

Closed

Description

@flyingrobots

Audit refs: AUD-2026-06-28-V01 §4.3 (Dependency Update); AUD-2026-06-28-V03 §2.3 Gap 2

Dependency posture is excellent (3 runtime deps, clean licenses) but unenforced — a future bad dependency wouldn't be caught automatically. Add cargo-deny (advisories + licenses + bans + sources) to CI so the clean posture becomes a gate.

Acceptance criteria

  • deny.toml added (Apache-2.0-compatible license allowlist) and a CI job runs cargo deny check; green on current deps.
  • Update docs/audit/2026-06-28_code-quality.md §4.3 and docs/audit/2026-06-28_ship-readiness.md §2.3 Gap 2: add ✅ Addressed (YYYY-MM-DD, #PR).

Activity

  1. coderabbitai commented on Jun 29, 2026

    @coderabbitai
    🔗 Related PRs

    #26 - docs: add release process topic shelf [merged]
    #32 - docs: add workflow standards [merged]
    #43 - Prepare v0.5.0-alpha.1 release [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions