Repository navigation
Fix policy, discovery, advisory metadata, and SBOM correctness gaps - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Source-based bug investigation in a fresh temporary GitHub clone. Reproductions preceded fixes, with repeated adjacent-path review and regression passes.
Validation
go test -race ./... -count=1passed on macOS arm64 / Go 1.23.4.See
docs/audits/2026-10-12.mdfor reproductions, compatibility notes, and remaining limitations.Review notes
Maintenance-enabled scores and some CVSS scope-changed scores change. Unknown policy fields, unsupported sources, and incomplete inventories now fail explicitly. SBOMs omit fabricated package checksums. Advisory cache entries are refreshed under a new namespace to retain affected-package data.
This is a post-v0.2.0 review branch. Main, the published binaries, and all release tags remain unchanged. No new release is requested by this PR. Passing checks do not establish that a last bug has been found.
Final GitHub verification
Latest head:
b640e117a60255732a6e723762d9c0b8a509c415.14 checks passed, 2 skipped, 0 failed.
The first PR exposed an additional CI-only defect: unsupported Gitleaks Action inputs and a missing PR token. Follow-up commit replaces the wrapper with the pinned CLI and verifies a synthetic credential positive control locally. No additional token permission was introduced.