Static analysis for vibe-coded apps. Flags the security, reliability, performance, and AI quality issues that Cursor, v0, Bolt, and Copilot create — hallucinated imports, missing auth, hardcoded secrets, unvalidated server actions, and more. Zero config, no LLM, 52 rules.
Production readiness for vibe-coded apps — know your AI code is ready to ship
2026-11-15
星數
—
工具
—
可用率
—
npx prodlint
prodlint v0.10.4
Scanned 148 files · 2 critical · 5 warnings · 1 info
src/app/api/checkout/route.ts
12:1 INFO No rate limiting — anyone could spam this endpoint and run up your API costs rate-limiting
28:5 WARN Empty catch block silently swallows error shallow-catch
src/actions/submit.ts
5:3 CRIT Server action uses formData without validation next-server-action-validation
↳ Validate with Zod: const data = schema.safeParse(Object.fromEntries(formData))
src/lib/db.ts
1:1 CRIT Package "drizzle-orm" is imported but not in package.json hallucinated-imports
Scores
security 72 ████████████████░░░░ (8 issues)
reliability 85 █████████████████░░░ (4 issues)
performance 95 ███████████████████░ (1 issue)
ai-quality 90 ██████████████████░░ (3 issues)
Overall: 82/100 (weighted)
2 critical · 5 warnings · 4 info
Why?
Vibe coding is the fastest way to build. Shipping fast means knowing your code is production-ready — not just that it compiles. Hardcoded secrets, hallucinated packages, missing auth, and XSS vectors pass type-checks and look correct — but they aren't ready for production.
prodlint checks what TypeScript and ESLint don't: whether your vibe-coded app is ready for production.
Install
npx prodlint # Run directly (no install)
npx prodlint ./my-app # Scan specific path
npx prodlint --json # JSON output for CI
npx prodlint --sarif # SARIF 2.1.0 for GitHub Code Scanning
npx prodlint --summary # Quick pass/fail + top 3 blockers
npx prodlint --profile startup # Only critical findings
npx prodlint --profile strict # All findings including info
npx prodlint --baseline .prodlint-baseline.json # Only new findings
npx prodlint --ignore "*.test.ts" # Ignore patterns
npx prodlint --min-severity warning # Only warnings and criticals
npx prodlint --quiet # Suppress badge output
Or install it:
npm i -D prodlint # Project dependency
npm i -g prodlint # Global install
52 Rules across 4 Categories
Security (27 rules)
Rule
What it checks
secrets
API keys, tokens, passwords hardcoded in source
auth-checks
API routes with no authentication
env-exposure
NEXT_PUBLIC_ on server-only secrets
input-validation
Request body used without validation
cors-config
Access-Control-Allow-Origin: *, wildcard + credentials escalated to critical
unsafe-html
dangerouslySetInnerHTML with user data
sql-injection
String-interpolated SQL queries (ORM-aware)
open-redirect
User input passed to redirect()
rate-limiting
API routes with no rate limiter
phantom-dependency
Packages in node_modules but missing from package.json
insecure-cookie
Session cookies missing httpOnly/secure/sameSite
leaked-env-in-logs
process.env.* inside console.log calls
insecure-random
Math.random() used for tokens, secrets, or session IDs
next-server-action-validation
Server actions using formData without Zod/schema validation
env-fallback-secret
Security-sensitive env vars with hardcoded fallback values
verbose-error-response
Error stack traces or messages leaked in API responses
missing-webhook-verification
Webhook routes without signature verification
server-action-auth
Server actions with mutations but no auth check
eval-injection
eval(), new Function(), dynamic code execution
next-public-sensitive
NEXT_PUBLIC_ prefix on secret env vars
ssrf-risk
User-controlled URLs passed to fetch in server code
path-traversal
File system operations with unsanitized user input
unsafe-file-upload
File upload handlers without type or size validation
supabase-missing-rls
CREATE TABLE in migrations without enabling RLS
deprecated-oauth-flow
OAuth Implicit Grant (response_type=token)
jwt-no-expiry
JWT tokens signed without an expiration
client-side-auth-only
Password comparisons or auth logic in client components
Reliability (11 rules)
Rule
What it checks
hallucinated-imports
Imports of packages not in package.json
error-handling
Async operations without try/catch
unhandled-promise
Floating promises with no await or .catch
shallow-catch
Empty catch blocks that swallow errors
missing-loading-state
Client components that fetch without a loading state
missing-error-boundary
Route layouts without a matching error.tsx
missing-transaction
Multiple Prisma writes without $transaction
redirect-in-try-catch
redirect() inside try/catch — Next.js redirect throws, catch swallows it
missing-revalidation
Server actions with DB mutations but no revalidatePath
missing-useeffect-cleanup
useEffect with subscriptions/timers but no cleanup return
hydration-mismatch
window/Date.now()/Math.random() in server component render path
Performance (6 rules)
Rule
What it checks
no-sync-fs
readFileSync in API routes
no-n-plus-one
Database calls inside loops
no-unbounded-query
.findMany() / .select('*') with no limit
no-dynamic-import-loop
import() inside loops
server-component-fetch-self
Server components fetching their own API routes
missing-abort-controller
Fetch/axios calls without timeout or AbortController
AI Quality (8 rules)
Rule
What it checks
ai-smells
any types, console.log, TODO comments piling up
placeholder-content
Lorem ipsum, example emails, "your-api-key-here" left in production code
hallucinated-api
.flatten(), .contains(), .substr() — methods AI invents
stale-fallback
localhost:3000 hardcoded in production code
comprehension-debt
Functions over 80 lines, deep nesting, too many parameters
codebase-consistency
Mixed naming conventions across the project
dead-exports
Exported functions that nothing imports
use-client-overuse
"use client" on files that don't use any client-side APIs
Smart Detection
prodlint avoids common false positives:
AST parsing — Babel-based analysis for 13 rules (imports, catch blocks, redirects, redirects in try/catch, SSRF, path traversal, JWT, HTML injection, hydration, transactions, env leaks, loops, SQL) with regex fallback
Monorepo support — npm/yarn/pnpm workspace dependencies resolved automatically
Posts a score breakdown as a PR comment, and fails the build when the scan finds critical
issues or the score is below threshold. Each release of the action runs its matching
prodlint version, so pinning the action (@v1, a version tag, or a commit SHA) also pins
the scanner.
Input
Default
Description
path
.
Path to scan
threshold
0
Minimum score to pass (0-100)
fail-on-critical
true
Fail when the scan finds critical issues; false reports them without failing
Adopt prodlint gradually without drowning in pre-existing findings:
# Save current state as baseline
npx prodlint --baseline-save .prodlint-baseline.json
# CI only fails on NEW findings
npx prodlint --baseline .prodlint-baseline.json
MCP Server
Use prodlint inside Cursor, Claude Code, or any MCP-compatible editor:
prodlint-mcp is a thin launcher for the server built into prodlint. It's published with
every prodlint release, so it always runs the matching scanner.
Ask your AI: "Run prodlint on this project" and it calls the scan tool directly.
Score, category scores, and findings most severe first. Every critical finding is listed, even past maxFindings.
scan-web
url
Site score, grade, and the 14 agent-readiness checks
Both tools return a Markdown summary plus structured output (structuredContent matching
each tool's outputSchema), and both are marked read-only (readOnlyHint), which hosted
reviewers such as GitHub Copilot code review require before they call an MCP tool.
Site Score
Check any deployed website for AI agent-readiness — 14 checks covering emerging standards like llms.txt, TDMRep, AgentCard, AI-Disclosure, HTTP Signatures (RFC 9421), and more.
MCP setup guide: prodlint.com/mcp — detailed editor setup for Claude Code, Cursor, Windsurf
prodlint is designed specifically for AI-generated code patterns. Every rule checks for production issues that AI coding tools consistently create — not style nits.