Skip to content

The problem list is free. A fix prompt for each one is $9.

See pricing

Windsurf

Exposed git metadata on a Windsurf app

Windsurf's agent edits a project you deploy yourself. The public check is of that deployment. Secrets the agent wrote into client code show up if the browser downloads them.

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 read the Windsurf session or your local files.

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 Windsurf project?

No. The scan does not read the Windsurf session or your local files.

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.

Free public scan