Security gaps
Find risky patterns and weak defaults before they reach production.
Free local code scan
A launch-readiness scan that runs locally. No signup. No code uploaded anywhere. Every finding and fix prompt is free.
$ npx should-i-ship@latest scanNode.js 20+ · macOS, Linux, and Windows
What it checks
Focused checks for the issues that matter before real users and real traffic arrive.
Find risky patterns and weak defaults before they reach production.
Catch credentials and tokens that should never live in source code.
Flag routes and actions that accept requests without authorization checks.
Spot webhook handlers that trust payloads without verifying signatures.
Identify public endpoints that can be abused or run up your bill.
Surface unbounded AI calls, expensive loops, and scaling surprises.
Useful output
The terminal gives you the priority list. The generated report gives you the detail.
Should I Ship
==============
Score: 68/100
Launch verdict: Fix before traffic
Findings: 6 total (1 critical, 2 high)
Fix-first plan
1. CRITICAL SECURITY: Exposed API key
Launch impact: Blocker
Fix: Move the key to an environment variable.
2. HIGH SECURITY: API route missing auth
Launch impact: Fix before trafficScore: 68/100
Launch verdict: Fix before traffic
A credential appears to be hardcoded in source code.
Location: src/lib/client.ts:12
Suggested fix: Move the key to an environment variable and rotate it.
Private by default
01 Scans git-visible files, including uncommitted work.
02 Respects ignored files such as .env.
03 Writes the complete report to .should-i-ship/.
04 Uploads neither source code nor findings.
Zero to Build
Zero to Build fixes these issues and builds custom apps.
Work with Zero to Build →