What it finds on a demo project

The CLI looks for values that resemble credentials in source, AI and MCP config and agent instruction files, tokens written into .npmrc, .env files that .gitignore doesn't cover, and names that suggest secrets in browser-public variables. It reads the files in your checkout, not your Git history.

SiteCMD CLI 2.0.0
Demo project: Secrets in code and config
npx sitecmd audit .
SiteCMD Code Scan - .
Checked: November 9, 2026
Framework: Express
Issues: 6 total | critical 0 | high 5 | medium 1 | low 0

High (5)
- [Dependencies · supply-chain] AI or MCP config may contain a hardcoded credential - .claude/settings.json:3
- [AI Setup · ai-scaffolding] Credential-shaped literal in .mcp.json - .mcp.json:6
- [Dependencies · supply-chain] Project .npmrc contains a literal registry auth value - .npmrc:1
- [Security · security] Source file contains a credential-shaped literal - src/index.js:4
- [Security · security] Possible sensitive credential uses a client-public environment name - web/client.js:1

Medium (1)
- [Security · security] .gitignore does not cover environment files present in the project - .gitignore

Your code passes? Now watch your site.

Join the waitlist

Add .env to .gitignore and untrack a committed copy

Keep local credential files out of future commits. An ignore rule doesn't remove a file Git already tracks, so check that separately. GitHub's sensitive-data guidance explains the cleanup decisions.

Review NEXT_PUBLIC environment variables for sensitive values

Next.js can replace a direct reference to a NEXT_PUBLIC_ variable with its build-time value in browser JavaScript. Make sure that value is meant to be public. Next.js documents the substitution.

Frequently asked questions

Should I remove .env from Git history before rotating a secret?

Revoke or rotate an exposed credential first. Then decide whether you still need to rewrite history; doing so can affect existing clones and collaboration.

Confirm you're a person