WholestackSign inIs your app safe to ship? Get a verdict, not a vibe.
Built it on Lovable, Bolt, v0, Cursor, Replit — or by hand? Point us at the repo. The same fail-closed gate every WholeStack build passes runs on your code and says SHIP or NO_SHIP, with the real blockers listed. Free — sign in with GitHub to run it.
What the gate looks for
Leaked secrets
Service-role keys, API tokens, and credentials sitting in the client bundle or committed to the repo.
Auth & authz gaps
Endpoints that handle sensitive data with nobody checking who's asking.
Fake-success UI
Handlers that swallow errors and paint green anyway — “looks like it worked” lies.
Hallucinated imports
Fabricated packages and non-existent APIs AI tools invent under pressure.
Taint flows
Untrusted input reaching queries, shells, or rendered HTML without sanitization.
Supply chain
Phantom and look-alike dependencies that don't belong in your lockfile.
We never show a green we didn't earn. This is a static scan with TS/JS depth — a clean result means no blocking anti-patterns found, not a correctness or intent guarantee. When a repo can't be meaningfully scanned the verdict is unverified, never a fake pass. A NO_SHIP comes with the blockers listed — and a $25 Fix Pass that regenerates a SHIP-verified build if you want it fixed.
Shipping a smart contract instead? Scan Solidity with the formal prover →
Same gate as every WholeStack build. Shipped proofs publish to proven.money.