Support stable GO/Debian advisory IDs and scoped occurrence reviews #63

Merged
gitchegumi merged 2 commits from kiyi/stable-upstream-risk-review into main 2026-09-27 13:14:04 -05:00
Member

Changes

  • Extend exact vulnerability selectors to GO, DLA and DSA IDs, with optional stable target/count maps.
  • Add schema 2 image configuration reviews keyed by Dockerfile rule ID, image repository, owning package/version, component, severity and exact stable target/count. Schema 1 remains supported for existing reviews and rejects configuration entries.
  • Preserve reviews across source-line, temporary archive and release-provenance changes. Changed findings and excess counts remain blocking.
  • Accept package contexts supplied by the owning caller from verified archived metadata. Missing context remains blocking.
  • Allow bounded partial counts during image preflight so malware and SBOM follow-ups still run; final evaluation requires exact counts. Secret, malware, scanner-error and unreviewed-finding gates remain required.

Validation

49 source tests passed: 36 policy/security, 6 mocked image-preflight and 7 reporting tests. Tests cover schema migration, stable rule/path identity, archive and provenance movement, package/version changes, missing context, count changes and required follow-ups. git diff --check passed. No local container/runtime tests were run.

Adoption

Prepared for v1.23.0 after review/merge and operator-controlled publication; no released tag is claimed. The current implementation is a9ac5bd5ad813854a666451930134bfb590e6d1f. Migrate consumers and policy schemas together. Platform is preparing the six owner-accepted Core/init configuration findings from run 4675, expiring 2026-10-27; these are risk acceptances, not false-positive or remediation claims.

## Changes - Extend exact vulnerability selectors to GO, DLA and DSA IDs, with optional stable target/count maps. - Add schema 2 image configuration reviews keyed by Dockerfile rule ID, image repository, owning package/version, component, severity and exact stable target/count. Schema 1 remains supported for existing reviews and rejects configuration entries. - Preserve reviews across source-line, temporary archive and release-provenance changes. Changed findings and excess counts remain blocking. - Accept package contexts supplied by the owning caller from verified archived metadata. Missing context remains blocking. - Allow bounded partial counts during image preflight so malware and SBOM follow-ups still run; final evaluation requires exact counts. Secret, malware, scanner-error and unreviewed-finding gates remain required. ## Validation 49 source tests passed: 36 policy/security, 6 mocked image-preflight and 7 reporting tests. Tests cover schema migration, stable rule/path identity, archive and provenance movement, package/version changes, missing context, count changes and required follow-ups. `git diff --check` passed. No local container/runtime tests were run. ## Adoption Prepared for v1.23.0 after review/merge and operator-controlled publication; no released tag is claimed. The current implementation is `a9ac5bd5ad813854a666451930134bfb590e6d1f`. Migrate consumers and policy schemas together. Platform is preparing the six owner-accepted Core/init configuration findings from run 4675, expiring 2026-10-27; these are risk acceptances, not false-positive or remediation claims.
Support stable advisory IDs and scoped vulnerability occurrence reviews
All checks were successful
Workflow acceptance / acceptance (pull_request) Successful in 1m52s
Repository security / security-1 (pull_request) Successful in 4m56s
Library checks / tests (pull_request) Successful in 4m55s
247f4d259a
Support scoped upstream image configuration acceptance
All checks were successful
Workflow acceptance / acceptance (pull_request) Successful in 2m8s
Repository security / security-1 (pull_request) Successful in 2m48s
Library checks / tests (pull_request) Successful in 3m2s
a9ac5bd5ad
gitchegumi approved these changes 2026-09-27 13:13:13 -05:00
gitchegumi deleted branch kiyi/stable-upstream-risk-review 2026-09-27 13:14:04 -05:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Homelab/workflows!63
No description provided.