Skip to content

docs(security): the settled exceptions that stay say why - #51

Merged
maksimtech merged 1 commit into
mainfrom
chore/settled-exceptions-reviewed
Oct 15, 2026
Merged

maksimtech merged 1 commit into
mainfrom
chore/settled-exceptions-reviewed

Conversation

@maksimtech

Copy link
Copy Markdown
Owner

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 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.

Checks

  • tests/test_security_exceptions.py, tests/test_exceptions_epss.py and tests/test_nis2_evidence.py pass locally.
  • The text added to each entry is wrapped at 80 columns with TOML line continuations, and tomllib parses the file.

🤖 Generated with Claude Code

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
maksimtech enabled auto-merge (squash) October 15, 2026 12:30
@codspeed

codspeed Bot commented Oct 15, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

⚠️ 11 benchmarks spent significant time in system calls

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

✅ 17 untouched benchmarks


Comparing chore/settled-exceptions-reviewed (ab24418) with main (658965e)

Open in CodSpeed

@sonarqubecloud

Copy link
Copy Markdown

@codecov

codecov Bot commented Oct 15, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@maksimtech
maksimtech merged commit 29669d2 into main Oct 15, 2026
25 checks passed
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