Remove public Homebrew tap and Scoop bucket from code-fleet-watch denylist #700
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#700
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Outcome
Remove the Homebrew tap and Scoop bucket rules from the code-fleet-watch denylist. Both repositories are public distribution channels and must not produce product-policy findings.
Evidence
cli-guard#266 currently reports four findings under these aliases:
product:repo-homebrew-tapinREADME.mdanddocs/specgen-install.mdproduct:repo-scoop-bucketinREADME.mdanddocs/specgen-install.mdThose files correctly document the public installation URLs. The scanner is reporting its configured rules as designed. The denylist input is wrong.
Work
product:repo-homebrew-tapandproduct:repo-scoop-bucketfrom the SSM-owned code-fleet-watch denylist.code-fleet-watch-denylistWard verb without printing decoded terms.Acceptance
Closing as superseded by #830. Retiring code-fleet-watch removes the denylist entirely, so there is no rule left to correct.
The underlying observation still stands and is worth recording: the Homebrew tap and Scoop bucket are public distribution channels, and any future scanner that treats their URLs as private terms will produce the same false findings.