Replit
Exposed git metadata on a Replit app
A Replit deployment is an ordinary website. The page, its same-origin scripts, and the headers from that host are what a visitor receives, and what this scan reads.
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 Replit API, the workspace, and secrets that exist only in Replit's server environment are outside the fetch.
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 Replit project?
No. The Replit API, the workspace, and secrets that exist only in Replit's server environment are outside the fetch.
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.