Cursor
Firebase security rules 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.
What a public Firebase config means, and why rules are a separate check.
What the scan can see
A Firebase web config in the client is a note. The apiKey in that config is meant to be public. A Google API key string and any other secret in the same files are reported with their own severity.
What it does not do
Firestore, Realtime Database, and Storage rules are not downloaded, and the scan does not try an anonymous read. Rules stay in the locked section of the report until domain ownership exists.
The scan does not open the Cursor workspace, the chat, or git history on your laptop.
What to do next
Open the Firebase console and read the rules for each database and bucket. Hiding the web apiKey does not protect data. Rules do.
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 firebase security rules is fully fixed?
Firestore, Realtime Database, and Storage rules are not downloaded, and the scan does not try an anonymous read. Rules stay in the locked section of the report until domain ownership exists.
What should I do if the scan finds it?
Open the Firebase console and read the rules for each database and bucket. Hiding the web apiKey does not protect data. Rules do.
Scan a URL you own
The same free check as the homepage. You confirm the app is yours before it runs.