Repository navigation
chore(security): review the acl exception due on 2026-11-30 - #87
Merged
Merged
Conversation
Security upkeep after the 2026-11-16 audit: review the acl exception due on 2026-11-30; no posture verdict on a failed Scout scan; Dependabot reads uv.lock. The exceptions were read again on 2026-11-17 against the Debian security tracker and archive, and against the image; run on the live alerts, this Radar's own gate is green on 2026-11-17 and 2026-12-01. Details per entry in the CHANGELOG and in the entries themselves. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # CHANGELOG.md
Merging this PR will not alter performance1 warning
Comparing |
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
On 2026-11-30 exceptions in
SECURITY-EXCEPTIONS.tomlreach their review date, and from 2026-12-01 Security Posture would have failed on its own in every Radar. This pull request is that review, plus two gaps the 2026-11-16 audit found.What
The one entry due on 2026-11-30:
Security Posture gives no verdict on a failed Docker Scout scan. It ran on every Scout
workflow_run, failed ones included. On 2026-11-16 exeradar's Scout stopped on a 403 before scanning, and the gate went green on the previous scan's alerts. It now runs on aworkflow_runonly when the scan succeeded, as exeradar#39 does. Push, PR, schedule and manual runs are unchanged. Test:test_a_failed_scan_triggers_no_verdict.Dependabot reads
uv.lockfor security updates. patchradar'suv.lockheld opentelemetry-api 1.45.1 with a Dependabot alert from 2026-11-14, and no pull request came, because no entry ofdependabot.ymlreaduv.lock. Auventry withopen-pull-requests-limit: 0stops version updates for uv, so pip's remain the one weekly stream; security updates are not limited by it. Test:test_uv_lock_gets_security_updates_and_no_version_updates.Verification
tools/security_exceptions.review, run on the new file against the live code scanning alerts of main (50 open, plus fixed and dismissed):ruffis clean.🤖 Generated with Claude Code