Stripe
Webhook signing secrets are separate from API keys and must be rotated in the webhook config, not just the API keys page.
ShipSafe is the security track inside Early AI-dopters, a Skool community for people shipping with AI. Join the community to unlock the 12-week cohort — a human coach reviews the code your AI wrote before strangers do.
You have 1 critical and 1 high sitting in a repo where the repo has been public 14 days with 3 forks. The keys are live and someone else can see them. Rotate Stripe first, then OpenAI; the report below has the rotation links. Forensics can wait until your keys are dead.
Webhook signing secrets are separate from API keys and must be rotated in the webhook config, not just the API keys page.
Old keys keep working for ~60 seconds after revocation due to edge caching.
You point Sentinel at your repo. It runs on your machine or ours and lands findings inside your ShipSafe project. No code leaves your control without you seeing it.
Secrets, private paths, and identifying detail are stripped. A human coach (right now, that’s Ty) walks every finding, drops the noise, and keeps what matters for your stack.
One published report. Only you see it. In the weekly live session, we work through it together — fix first, learn as we go.
ShipSafe is the coaching platform for Early AI-dopters— a Skool community for people shipping with AI who don’t want to ship a breach. New members get auto-invited the moment they join the community. No waitlist, no gatekeeping.
I shipped a side project on Sunday, leaked a Stripe key in commit two, and didn’t notice until Wednesday’s session. Ty walked me through the rotation in ten minutes. Forensics after. Rotate first.