Repository navigation
docs(security): the settled exceptions that stay say why - #51
Merged
Merged
Conversation
The gate lists these entries as settled: their alerts are closed because the scanners stopped reporting them, not because anything left the image. `patchradar debian` on 2026-10-15 still reports gcc-14 no-dsa in trixie at 14.2.0-19 (fix only in sid, 14.4.0-3), so the flaws are still present and only the reporting changed. The entries stay, and each now records when the scanner fell silent and what Debian said, in the words the CVE-2026-82560 entry already uses. Deleting a flaw that is demonstrably present because a scanner fell silent is the one direction the file must not drift in. Checked, not inferred: a script read this repository's live open and closed code-scanning alerts and listed every kept settled entry that did not say why (4 before, 0 after), and tools/security_exceptions.py on the same alerts still exits 1, only for CodeQL #60, which #50 fixes. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
maksimtech
enabled auto-merge (squash)
October 15, 2026 12:30
Merging this PR will not alter performance
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.



Why and what
The gate lists these entries as settled: their alerts are closed because the
scanners stopped reporting them, not because anything left the image.
patchradar debianon 2026-10-15 still reports gcc-14 no-dsa in trixie at14.2.0-19 (fix only in sid, 14.4.0-3), so the flaws are still
present and only the reporting changed. The entries stay, and each now
records when the scanner fell silent and what Debian said, in the words the
CVE-2026-82560 entry already uses. Deleting a flaw that is demonstrably
present because a scanner fell silent is the one direction the file must
not drift in.
Checked, not inferred: a script read this repository's live open and closed
code-scanning alerts and listed every kept settled entry that did not say
why (4 before, 0 after), and tools/security_exceptions.py on the same
alerts still exits 1, only for CodeQL #60, which #50 fixes.
Checks
tests/test_security_exceptions.py,tests/test_exceptions_epss.pyandtests/test_nis2_evidence.pypass locally.tomllibparses the file.🤖 Generated with Claude Code