Vibe Code Check
Pre-launch checklist

CHECK THIS BEFORE YOU SHIP.

If the app was built quickly, AI-assisted, or stitched together under pressure, this is the short list that keeps launch day from turning into cleanup day.

SECRETS AUTH VALIDATION RATE LIMITS

Start here

The basics that matter most before real users show up.

01
Secrets are actually private

Check the repo, build output, screenshots, demo files, and client-side code for keys, tokens, and passwords.

02
Protected routes are protected

Verify auth and roles on the routes that handle user data, admin actions, payments, and anything expensive.

03
Inputs are validated on the server

Forms, API routes, AI prompts, and uploads should all be checked where users cannot bypass them.

Full checklist

Use this like a final pre-ship pass.

Secrets safety

No credentials in repo files, browser code, screenshots, docs, or example env files.

Auth and roles

Sensitive routes only work for the users and roles you intended.

Server validation

The backend rejects bad input even if the frontend looks fine.

Rate limits

Login, signup, contact forms, and costly endpoints are protected from abuse.

Logging and privacy

Errors are useful without leaking user data, tokens, or private payloads.

Trust pages

You have basic metadata, a privacy page, and a clear security contact path.

Next step

Do not guess.

Use the checklist, then run the scan so you know what still needs work.

Open the scanner