Skip to content

fix(supply-chain): keep advisories out of the required check (Y44-Y46) - #8

Merged
constantin-jais merged 1 commit into
migrate/recover-codefrom
work/documents-75-y44
Oct 9, 2026
Merged

constantin-jais merged 1 commit into
migrate/recover-codefrom
work/documents-75-y44

Conversation

@constantin-jais

Copy link
Copy Markdown
Contributor

Owner-arbitration: 2026-10-09

What

  • Y44 / I-26: check-dependency-policy.ts runs --locked check bans licenses sources; advisories is removed from the required verdict (a test pins the list).
  • Y45: base allowlist admits Apache-2.0 WITH LLVM-exception (ADR-0042 §11, doctrine PR project-governance#62).
  • Y46: confidence-threshold = 0.9; multiple-versions = "warn" kept.
  • deny.toml stays byte-identical across the 10 Rust repositories.

Local result (cargo-deny 0.19.5)

     bans ok: 0 errors, 9 warnings, 0 notes
 licenses ok: 0 errors, 0 warnings, 98 notes
  sources ok: 0 errors, 1 warnings, 0 notes
Dependency policy verified: bans, licenses, sources hold for 1 manifest(s), 99 locked package(s) inspected

No workflow, Cargo.lock, rev or pin file is touched; no advisory waiver is added.

https://claude.ai/code/session_01Qw4AExV42cXJ67Sj9dqLVf

- Y44 / I-26: the required check runs `bans licenses sources` only, still
  with --locked. An advisory verdict depends on the RustSec database of
  the day; a fleet advisory control notifies on it without blocking.
- Y45: the base allowlist admits `Apache-2.0 WITH LLVM-exception`
  (ADR-0042 §11).
- Y46: `confidence-threshold` is 0.9; `multiple-versions` stays "warn".

deny.toml stays byte-identical across the Rust repositories.

Owner-arbitration: 2026-10-09
Claude-Session: https://claude.ai/code/session_01Qw4AExV42cXJ67Sj9dqLVf
Signed-off-by: Constantin <74049135+constantin-jais@users.noreply.github.com>
@constantin-jais
constantin-jais merged commit e1249c5 into migrate/recover-code Oct 9, 2026
1 check passed
@constantin-jais
constantin-jais deleted the work/documents-75-y44 branch October 9, 2026 12:29
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