Ship it safely

1. 1

   @shipcheck/env-secrets-check

   Check your repo for leaked secrets before you push or launch: .env files git tracks or will pick up, .env files hiding in git history, server keys behind NEXT_PUBLIC_ or VITE_ prefixes that ship to the browser, provider key shapes (Stripe, AWS, GitHub, OpenAI, Anthropic, Supabase service_role), and passwords hardcoded in code. Reports names and redacted hints, never the values.

   Resolves to 1.0.0 (range ^1.0.0)

2. 2

   @shipcheck/supabase-rls-audit

   Audit row level security in your Supabase migrations before you launch. Finds tables with RLS off, policies that let anyone write, policies that trust user_metadata, views that skip RLS, and risky SECURITY DEFINER functions, then drafts a fix migration for you to review. Reads .sql files only and never touches your database.

   Resolves to 1.0.0 (range ^1.0.0)

3. 3

   @shipcheck/stripe-webhook-hardening

   Find your Stripe webhook handlers and harden them: verify the Stripe-Signature header, use the raw body, keep the signing secret in env, process each event once, reject bad signatures with 400, and fulfill orders from the webhook rather than the success page. Reads your code and proposes diffs; never calls Stripe.

   Resolves to 1.0.0 (range ^1.0.0)

4. 4

   @shipcheck/launch-checklist

   A pre-launch check for your first real app. Reads your project, detects the stack (Supabase, Stripe, Next.js, auth, email), and writes a checklist split into blockers, first-week items, and later, with evidence from your code for each item it could verify. Covers data access, payments, secrets, auth, abuse limits, errors and monitoring, backups, email deliverability, legal pages, and SEO basics.

   Resolves to 1.0.0 (range ^1.0.0)

5. 5

   @shipcheck/deploy-doctor

   Paste a failed Vercel or Netlify build log and get the most likely cause and a fix you can apply. Recognizes about twenty common failures: letter-case import errors, missing packages, missing env vars, prerender errors, window is not defined, lockfile drift, peer dependency conflicts, wrong Node version, out of memory, wrong output or root folder, oversized functions, and more.

   Resolves to 1.0.0 (range ^1.0.0)

This stack needs no environment variables.

Names only. Values stay on your machine.