Base44
Exposed git metadata on a Base44 app
Base44 hosts the app it builds. The hosted URL is the thing to paste. Public files and headers on that host are in scope.
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.
Base44 project settings and databases are not opened. The scan does not log in as a user of the app.
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 Base44 project?
No. Base44 project settings and databases are not opened. The scan does not log in as a user of the app.
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.