Ai builder fingerprint exposed
"Ai builder fingerprint exposed" is a low-severity ai exposure finding ShipReady reports when it observes the condition directly on your site. Worth fixing. Small individually, and they accumulate.
How ShipReady detects it
AI-specific exposure — the product's differentiating module. Covers two distinct failure modes of AI-built applications: 1. Tooling artifacts deployed by accident. AI coding tools generate config and instruction files at the repo root; developers who push a whole repo (rather than just its build output) to static hosting serve them publicly. Some are merely instructions; others hold live API keys. 2. Secrets promoted into the client bundle via a PUBLIC env var prefix. This is the single most characteristic AI-app mistake: AI assistants correctly explain that a variable must be prefixed (NEXT_PUBLIC_, VITE_, ...) to be readable in the browser, and developers apply that prefix to a *server* secret. The bundler then inlines the real value into JavaScript that anyone can read. Both are confirmed by observation, never inferred from framework fingerprints alone.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.3.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
Your deployed site advertises that it was built with {builder}. Remove the marker: if it is a deployed repository file (.cursorrules, CLAUDE.md, .bolt/, .replit, .windsurfrules), stop shipping repository files to your host by deploying only your build output and adding those paths to .gitignore or your host's ignore file. If it is an injected script or badge, remove it from your HTML template. Then treat this as a prompt to check the findings that actually matter: applications built with AI tools most commonly ship with database Row Level Security disabled and server credentials promoted into client-side environment variables, so work through the Database Access and Exposed Secrets sections of this report before anything else. Removing the fingerprint alone changes nothing about those.Frequently asked questions
- What does "Ai builder fingerprint exposed" mean?
- "Ai builder fingerprint exposed" is a low-severity ai exposure finding ShipReady reports when it observes the condition directly on your site. Worth fixing. Small individually, and they accumulate.
- How serious is it?
- ShipReady rates this low. Worth fixing. Small individually, and they accumulate.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.
Related checks
Does your site have this?
ShipReady checks this and 73 other things across up to ten pages of your site. Free, no signup.
Scan my site