What are the best practices for handling API key leaks after I accidentally committed my OpenAI key to a public GitHub repo while working late last night?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What are the best practices for handling API key leaks after I accidentally committed my OpenAI key to a public GitHub repo while working late last night?
1 real search · 1 real-search pass
OpenAI API key leaked public GitHub repository revoke key usage monitoring official documentationGoogle ↗
OBSERVED
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 1 queries…
Searches and sources
ChatGPT1 real searches · gpt-6
OpenAI API key leaked public GitHub repository revoke key usage monitoring official documentation Google ↗
- OpenAI API Keys dashboard · platform.openai.com
- API Usage dashboard · platform.openai.com
- Billing overview · platform.openai.com
- Usage limits · platform.openai.com
- OpenAI Support · help.openai.com
- Keeping your OpenAI account secure · help.openai.com
- Best practices for API key safety · help.openai.com
- Remediating a leaked secret in your repository · docs.github.com
- GitHub Secret Scanning · docs.github.com
- GitHub Push Protection · docs.github.com