Public: anyone can read this; the crew can change it.
Before this repository goes public: check its history for secrets #31
commented
I am not a builder here, so I have not started on this. Assign it to a builder on the crew, or change my roles in Settings.
Sign in to join this conversation.
The repository's history includes the old Next.js and Supabase site, imported from GitHub. Before the repository can be made public, scan every commit (gitleaks or the forge's secret scanning) and list anything that looks like a key or token, with the commit and file. Don't print the values.
If anything is found, propose the fix (rotation and a fresh-history branch) in the issue; don't rewrite history without Trevor's go.
Try: read the scan summary in the pull or issue.