Go-based CLI tool that scans codebases for launch readiness, detecting missing configuration, security hygiene issues, secret leaks, and integration gaps before production deployment.
Preflight.sh is a command-line tool that scans your codebase for launch readiness. Identifies missing configuration, integration issues, security concerns, SEO metadata gaps, and other common mistakes before you deploy to production.
Don't embarrass yourself in production. Just run the command.
brew install preflightsh/preflight/preflight
npm install -g @preflightsh/preflight
go install github.com/preflightsh/preflight@latest
docker pull ghcr.io/preflightsh/preflight
curl -fsSL https://preflight.sh/install.sh | sh
Download the latest release from GitHub Releases.
From v0.23.0 each archive carries signed build provenance. To check that a download was built by this repo's release workflow:
gh attestation verify preflight_<version>_<os>_<arch>.tar.gz --repo preflightsh/preflight
# Initialize in your project directory
cd your-project
preflight init
# (asks before replacing an existing preflight.yml; --force skips the question)
# In a script or CI job, where nobody can answer, pass --yes to accept the
# detected defaults. Without it, init stops and writes nothing when its input
# ends before the questions do.
# Run all checks
preflight scan
# Scan a specific directory
preflight scan /path/to/project
# Run with verbose output (shows which files matched each check)
preflight scan --verbose
preflight scan -v # short form
# Run in CI mode with JSON output
preflight scan --ci --format json
# Run only specific checks, or skip some, for fast iteration
# (one-off; unlike `preflight ignore` it doesn't change preflight.yml)
preflight scan --only seo_meta,og_twitter
preflight scan --skip vulnerability,secrets
# Silence a check
preflight ignore sitemap
# Unsilence a check
preflight unignore sitemap
# List all check IDs
preflight checks
This repo includes a skills.sh-compatible agent skill at skills/preflight/SKILL.md. It gives coding agents a repeatable Preflight workflow: inspect preflight.yml, run CI-safe scans, triage findings, avoid unsafe ignores, rerun validation, and report residual launch risk.
List the skill from this repository:
# With Bun
bunx --yes skills add preflightsh/preflight --list
# Or with npm
npx --yes skills add preflightsh/preflight --list
Install only the Preflight skill:
# With Bun
bunx --yes skills add preflightsh/preflight --skill preflight
# Or with npm
npx --yes skills add preflightsh/preflight --skill preflight
Preflight is fully usable from the command line with no account. The optional dashboard at app.preflight.sh adds a hosted history of your scans and AI-generated fix suggestions for each finding. Your code never leaves your machine: scanning runs locally, and nothing is sent unless you publish. Dashboard bearer tokens are restricted to the origin that issued them, and authenticated redirects cannot cross origins or downgrade HTTPS.
security_headers, ssl, www_redirect, email_auth, debug_statements, error_pages, image_optimization, legal_pages, and the web standard file checks. debug_statements and image_optimization include up to five findings (file and line, or file and size).seoMeta layout path, and the env file names are removed, as are URL credentials, query strings, and fragments.secrets, vulnerability, env_parity, health_endpoint, stripe, index_now, every service check, and any "Check failed:" error.preflight.yml: project name, stack, URL origins, service declarations, and which checks are enabled. The IndexNow key, Stripe webhook URL, secrets allowlist, env file names, health path, layout path, and ignore list are dropped.Suggestions, file contents, audit tool output, and secret values are never sent.
Create a free account, then connect the CLI:
preflight auth login # opens your browser to authorize this CLI
preflight auth status # show who you're logged in as
preflight auth logout # remove stored credentials
Publish a scan to your dashboard with --publish. It prints a link to view the run. Publishing is best-effort: if you're offline or not logged in, the scan still runs and exits normally.
preflight scan --publish
On the dashboard you get each run's pass/warn/fail breakdown, the list of check outcomes, and a per-project history so you can see what changed between deploys.
You can also read that history from the terminal with preflight history:
preflight history # recent runs across your projects
preflight history --here # only the current project's runs
preflight history <run-id> # one run's full check results
preflight history --here --format json # machine-readable, for agents
Requires preflight auth login. --here matches runs to the current repository by its git remote, the same key used when publishing. An app scanned from a subdirectory of its repository (one app in a monorepo) is keyed by that subdirectory too, so apps/web and apps/api publish to separate dashboard projects. history --format json carries the same schema_version and cli_version fields as scan JSON.
On CI or another machine without a browser, log in with a token instead: preflight auth login --token - reads it from stdin, or set PREFLIGHT_TOKEN and run preflight auth login. Either way the token is checked and stored like a browser login; later commands read the stored credentials, not the variable.
Open any failed or warning check on a published run to generate a step-by-step fix tailored to your detected stack, with copy-ready commands and code.