feat(opencode): add shell env credential leak auditor#27075
Open
jinguanghai wants to merge 1 commit into
Open
Conversation
Adds an optional shellAudit() function that detects and redacts 8 types of credential patterns from shell environment variables. Redacts: AWS keys, GitHub tokens, Docker passwords, NPM tokens, PyPI tokens, LLM API keys, and any *_PASSWORD/_SECRET/_TOKEN. Tests: 6 test cases. No breaking changes. Closes anomalyco#27074
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
1 participant
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.
Adds an optional shellAudit() function that detects and redacts 8 types of credential patterns from shell environment variables.
Issue for this PR
Closes #27074
Type of change
What does this PR do?
Adds
tool/auditor.ts— a self-contained utility that scans shell environment variables for credential patterns (AWS keys, GitHub tokens, Docker passwords, NPM/PyPI tokens, LLM API keys) and redacts them. No integration into execute flow yet, making this PR minimal and non-breaking.How did you verify your code works?
6 test cases: redacts DEEPSEEK_API_KEY, GITHUB_TOKEN, etc; preserves safe vars (PATH, HOME, USER); handles short values; generates warning for redactions. All tests pass locally.
Checklist