secrets.sh --built — the scan stops at the repository, and secrets ship in the bundle #8
Labels
No Label
P0
P1
P2
release-blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/Project-Template#8
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
secrets.sh scans the staged diff and, with --tracked, the tracked tree. Neither sees the compiled output, which is the artifact users actually receive. An auditor of AI-built apps reports finding hardcoded keys in the frontend bundle of seven of eight apps in a single week.
Add a --built
mode to the existing script rather than writing a new one: it already resolves SECRETS_PATTERN_FILE and holds the project's own credential shapes. Add the patterns that recur in shipped bundles -- eyJ (a JWT header), service_role, anon, apikey, Bearer -- and the VITE_, REACT_APP_ and NEXT_PUBLIC_ prefixes, which are listed even when benign because 'deliberately shipped to the browser' is worth seeing enumerated.Verify: secrets.sh --built finds a planted fake credential in a scratch build directory and goes quiet once it is removed; docs/architecture/README.md records the new mode.