F20.2 — Dependency risk
| State | Closed |
| Parent | E20 |
| Iteration | Release 7 |
| Start Date | 2026-10-28 |
| Closed Date | 2026-10-28 |
| Predecessors | F20.1 |
| Source | Owner request, 2026-10-26 |
Stories: 3 Closed
| Story | State | Depends on |
|---|---|---|
S20.2.1 — Audit uv.lock in CI |
Closed | — |
S20.2.2 — Dependabot for uv |
Closed | — |
| S20.2.3 — Licence inventory | Closed | — |
Find vulnerable and unacceptably licensed dependencies before a release. CI
audits uv.lock, Dependabot watches the uv ecosystem as well as
github-actions, and a licence inventory lists every dependency's licence.
Design
Decided in ADR-0015: the audit is pip-audit and
the inventory is pip-licenses. The current commands and policy are in the
development guide.
S20.2.1 — Audit uv.lock in CI
State: Closed
Acceptance: CI fails or reports, as F20.1 decides, on a known-vulnerable locked dependency; a test or documented run shows a seeded vulnerable pin is caught.
S20.2.2 — Dependabot for uv
State: Closed
Acceptance: .github/dependabot.yml has a uv ecosystem entry beside
github-actions, and the file validates.
S20.2.3 — Licence inventory
State: Closed
Acceptance: CI produces a licence inventory of the locked dependencies, and a licence outside the policy F20.1 sets is flagged.
Acceptance
- S20.2.1: the audit step runs in CI and behaves as F20.1 decides.
- S20.2.2:
.github/dependabot.ymllistsuvandgithub-actions. - S20.2.3: the inventory artifact is produced on the main CI run.