Repository navigation
Conversation
Codex JSONL shared via a public URL can include API keys and tokens. Scan for a few common credential patterns, surface a warning toast, and note the risk in the README.
Author
|
Closing, since this repository has not merged outside pull requests and has been quiet since April. Happy to reopen if that changes. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Codex session JSONL can pick up API keys and tokens, and Euphony will happily load those files from a public URL. This adds a small best-effort scan for common OpenAI / GitHub / AWS credential shapes, shows a warning toast when they match, and documents the sharing risk in the README.
Fixes #2
Test plan
pytest tests/test_secret_scan.py tests/test_euphony.pypnpm exec tsc --noEmitsk-key and confirm the warning toast