Leaked API keys detected — 1 findings across 1 providers

Open Beginner friendly
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
firebase, google-cloud, javascript, react, redux
Domain
security

Research direction

Start by reviewing .env.development and the reported Google AI/Gemini finding. Revoke or rotate the exposed credential, remove it from public view, and confirm the file no longer contains the leaked key.

Written by the indexing model from the issue text.

Description

⚠ Leaked API Keys Detected

V1olet Security found 1 exposed API key(s) in this repository.

Please review and revoke/rotate the affected keys immediately.

Contact v1olet at v1olet.xyz

Findings Summary
  • google: 1 finding(s)
Detailed Findings
Google AI / Gemini
  • Partial Key: AIzaSy****
  • File: .env.development
  • Source: code`
  • Confidence: high
  • Verified: None

This report was auto-generated by KeyHunter v9 by v1olet Security — please revoke and remove the keys from public view immediately.

Dominant language
JavaScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.