v0
Exposed .env files on a v0 app
v0 generates UI you then deploy, often on Vercel. The scan starts at the deployed URL. It sees the shipped page, not the v0 chat that produced the components.
Public env files and why source maps are a separate problem.
What the scan can see
One GET each for /.env, /.env.local, and /.env.production. A body that looks like assignment lines is a critical finding. An HTML app shell at those paths is not treated as a leaked env file. /.git/HEAD and /.git/config are checked the same way.
What it does not do
Source maps (.js.map) are not requested. A map file can reveal original source, and this scan will not tell you if one is public. Local env files that were never deployed are also invisible.
A component that was generated but never deployed is not part of the check.
What to do next
If an env file was public, rotate every secret that was in it. Configure the host so those paths 404. Do not publish source maps for a production bundle.
Questions
Does this open my v0 project?
No. A component that was generated but never deployed is not part of the check.
Can the scan prove exposed .env files is fully fixed?
Source maps (.js.map) are not requested. A map file can reveal original source, and this scan will not tell you if one is public. Local env files that were never deployed are also invisible.
What should I do if the scan finds it?
If an env file was public, rotate every secret that was in it. Configure the host so those paths 404. Do not publish source maps for a production bundle.
Scan a URL you own
The same free check as the homepage. You confirm the app is yours before it runs.