Skip to content

Public API Key Leak #74

@ghost

Description

In this code there are several API Key Leaks I have discovered when doing analysis:

remote: —— Groq API Key ——————————————————————————————————————
remote: locations:
remote: - commit: 183528f
remote: path: notebooks/data_loading_processing.ipynb:23
remote: - commit: 342c4fb
remote: path: scratch.ipynb:517
remote: - commit: 0c54bd7
remote: path: scratch.ipynb:595
remote: - commit: d11fc22
remote: path: scratch.ipynb:595

remote: —— Groq API Key ——————————————————————————————————————
remote: locations:
remote: - commit: cce2a65
remote: path: XXXXXX.ipynb:26
remote: - commit: c4c312f
remote: path: XXXXXX.ipynb:26
remote: - commit: cce2a65
remote: path: XXXXXX.ipynb:84
remote: - commit: cce2a65
remote: path: XXXXXX.ipynb:237
remote: - commit: 00eb263
remote: path: scratch.ipynb:27

remote: —— Groq API Key ——————————————————————————————————————
remote: locations:
remote: - commit: 2a2c8e2
remote: path: main.py:28
remote: - commit: 00eb263
remote: path: server.py:28
remote: - commit: 2a2c8e2
remote: path: server.py:28
remote: - commit: 00eb263
remote: path: src/watch_utils.py:12
remote: - commit: 00eb263
remote: path: watch-api.ipynb:42

I suggest removing API key and using the environment variable, additionally I suggest purging the specific commit ID's from github history and revoking the current groq key.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions