Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False positive, Firebase API key #14

Open
19007361 opened this issue Jun 14, 2019 · 3 comments
Open

False positive, Firebase API key #14

19007361 opened this issue Jun 14, 2019 · 3 comments

Comments

@19007361
Copy link

Hello, and thank you for the GitGuardian service that you provide, it is really useful.

I want to point out that you should not auto-detect a Firebase API key as "compromised" since this is not a private key but a public key that any entity should access in order to connect to the Firebase API that was set up. Authentication allows only some/all end-users to access/modify/validate certain parts of it, so the API key is not the one that should be guarded.
https://stackoverflow.com/questions/35418143/how-to-restrict-firebase-data-modification

@jcubic
Copy link

jcubic commented Oct 10, 2019

Agree, Firebase in JavaScript are public keys, even that they look like private, everything what need to be in JS is public.

@fedorareis
Copy link

Per the documentation on Firebase Config files. API keys are considered unique but public information. https://firebase.google.com/docs/projects/learn-more#config-files-objects

@Unikore
Copy link

Unikore commented Jan 21, 2020

Just received an alert for the same thing, it's really a false positive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants