ASSAY / v0.1.0 — pre-deployment code auditor

Move fast with AI.
Without shipping vulnerabilities.

Assay audits your codebase before it hits production — catching hardcoded secrets, known CVEs, missing environment hygiene, and deployment anti-patterns. In seconds.

Built for AI-assisted developers, indie builders, and fast-moving teams who don't have a senior engineer reviewing every line.

Run audit freeView on GitHub

See it in action

$ assay audit ./my-startup

ASSAY AUDIT REPORT

────────────────────────────────

Score: 42 / 100

Files: 38

Issues: 7

Status: [ASSAY:BLOCK] Below threshold — review issues first

────────────────────────────────

[BLOCK] Hard blocks (1)

  ✕ Stripe live key detected in source file

    src/config.ts — "sk_live_ab..." found in plain text

    Fix: Move to .env and add .env to .gitignore. Rotate the key immediately.

[WARN] Friction gates (3)

  ⚠ lodash@4.17.20 has a known CVE

    CVE-2021-23337 — prototype pollution, affects versions below 4.17.21

    Fix: pnpm add lodash@latest

  ⚠ CORS wildcard origin detected

    src/server.ts allows requests from any origin (*)

    Fix: Restrict to your domain via process.env.ALLOWED_ORIGIN

  ⚠ Auth route has no rate limiting

    src/routes/auth.ts — /auth exposed to brute force

    Fix: Add express-rate-limit to /auth endpoints

[ADVISORY] Advisories (3)

  · Unpinned dependency: axios (^1.5.0)

  · No .env.example file found

  · Security headers not set (missing helmet)

Most tools tell you what's wrong. Assay tells you what to do about it — in plain language, before you deploy, with the specificity of a senior engineer who's seen this before.

What happens without it

Moltbook1.5M API tokens exposed

Founder shipped without a single security review. "I didn't write a single line of code for Moltbook."

✓ Assay would have blocked this — hardcoded tokens detected before commit.

Tea App72,000 images leaked including 13,000 government IDs

Firebase left with default settings. No authorization policies applied before launch.

✓ Assay would have flagged this — exposed API keys and missing security headers caught on first scan.

5,600 vibe-coded apps scanned2,000+ vulnerabilities — 400 exposed API keys

Most had never been audited before deployment. The code worked. The security didn't.

✓ Assay catches exactly this — secrets in source, unpinned CVE-affected deps, CORS wildcards.

Assay exists to prevent these exact scenarios.

One command. Before every deploy.

What it catches

[BLOCK]
Secrets detection
API keys, tokens, credentials in source
[WARN]
CVE scanning
Live npm audit — real-time vulnerabilities
[WARN]
Env hygiene
DEBUG flags, .env not in .gitignore
[WARN]
CORS policy
Wildcard origins dangerous in production
[WARN]
Rate limiting
Auth routes without brute-force protection
[ADVISORY]
Security headers
Helmet, XSS, CSRF, clickjacking

NOT this

✕ A linter — Assay doesn't care about style

✕ A test runner — Assay audits, not tests

✕ An enterprise SIEM — no setup, no agents

✕ A replacement for security engineers

THIS

✓ Pre-deployment audit — runs before you ship

✓ Plain language output — explains why it matters

✓ Actionable fixes — one sentence, do this

✓ Built for the vibe coding era

Get started in 30 seconds

$ npm install -g @assay-dev/cli

$ cd your-project

$ assay audit .

Run a free audit now

No account required. No data stored. Runs in your browser.