v0
Firebase security rules on a v0 app
v0 generates UI you then deploy, often on Vercel. The scan starts at the deployed URL. It sees the shipped page, not the v0 chat that produced the components.
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.
A component that was generated but never deployed is not part of the check.
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 v0 project?
No. A component that was generated but never deployed is not part of the check.
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.