I posted here a while back about Ship Safe, an open-source tool I built to catch things like leaked service_role keys or missing RLS policies when shipping fast. Some of the feedback was that a simple scanner wasn't enough, so I spent the last week building a way for the CLI to actually help you fix the issues it finds.
What is new:
.env file and replace the code with process.env.VAR_NAME.fix command: It generates your .env.example on the fly so your team stays in sync without you doing it manually.I am trying to bridge the gap between "vibe coding" speed and senior-level security. It is still 100% local, MIT licensed, and runs via npx.
npx ship-safe
DiscussionHealthy802 introduced an update to their open-source tool, Ship Safe, which now includes auto-remediation for security issues like leaked Supabase keys. The tool can automatically move hardcoded secrets to a .env file and improve team synchronization by generating .env.example files. It also includes deeper checks for Supabase-specific security concerns.
Good but is it safe, and will not steal credential?