Replit
Firebase security rules 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.
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 Replit API, the workspace, and secrets that exist only in Replit's server environment are outside the fetch.
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 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 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.