Repository navigation
feat: expand secure-by-default credential detection - #1
Merged
Merged
Conversation
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.
What changed
Expands the always-on guard patterns so a fresh install protects more provider credentials without requiring a custom
.gitpublic/scan.Added built-in detection for:
ASIA)Safe-by-default design
The new patterns are limited to recognizable provider-specific prefixes and structures. Broad assignment-based heuristics such as
accessToken = ...were intentionally excluded because they caused noisy false positives on normal source code.Tests
46 passedpython -m py_compilepassesgit diff --checkpassesTest credentials are assembled from string fragments so GitHub push protection does not mistake fixtures for leaked live secrets.