Cursor
Exposed git metadata on a Cursor app
Cursor writes the repo on your machine. Visitors see the host you deployed to. A key in a local .env is invisible here. A key compiled into the deployed JavaScript, or returned at /.env, is not.
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.
The scan does not open the Cursor workspace, the chat, or git history on your laptop.
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 Cursor project?
No. The scan does not open the Cursor workspace, the chat, or git history on your laptop.
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.