v0
Exposed git metadata 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.
A public .git directory on the deployed host.
What the scan can see
/.git/HEAD and /.git/config are fetched once each. A real git response is critical. The report can name the remote host. It does not keep the remote username or token. An HTML shell is ignored.
What it does not do
This is not a clone of the repository and not a history dump. Other git paths are not requested.
A component that was generated but never deployed is not part of the check.
What to do next
Stop serving .git. If a token was in the remote URL, revoke it. Treat the repo as copied if HEAD was public.
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 git metadata is fully fixed?
This is not a clone of the repository and not a history dump. Other git paths are not requested.
What should I do if the scan finds it?
Stop serving .git. If a token was in the remote URL, revoke it. Treat the repo as copied if HEAD was public.
Scan a URL you own
The same free check as the homepage. You confirm the app is yours before it runs.