https://github.com/ericzon/git-secrets-test
Project just to test git secret
https://github.com/ericzon/git-secrets-test
Last synced: over 1 year ago
JSON representation
Project just to test git secret
- Host: GitHub
- URL: https://github.com/ericzon/git-secrets-test
- Owner: ericzon
- Created: 2020-07-24T16:18:15.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2020-07-24T16:19:40.000Z (almost 6 years ago)
- Last Synced: 2025-01-23T22:17:48.624Z (over 1 year ago)
- Language: JavaScript
- Size: 1.95 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
GIT SECRETS test
================
Adding a new password pattern:
git secrets --add 'MyPASSWORD[0-9]+'
Listing current patterns in **this** repository:
git secrets --list
```
secrets.patterns MyPASSWORD[0-9]+
```
Using as git pre-hook:
git secrets --install
```
✓ Installed commit-msg hook to .git/hooks/commit-msg
✓ Installed pre-commit hook to .git/hooks/pre-commit
✓ Installed prepare-commit-msg hook to .git/hooks/prepare-commit-msg
```
Example of output when detects any password pattern in the code:
```
git commit -m "update: trying error again"
index.js:1:const password=process.env.USER_PASSWORD || 'MyPASSWORD666';
[ERROR] Matched one or more prohibited patterns
Possible mitigations:
- Mark false positives as allowed using: git config --add secrets.allowed ...
- Mark false positives as allowed by adding regular expressions to .gitallowed at repository's root directory
- List your configured patterns: git config --get-all secrets.patterns
- List your configured allowed patterns: git config --get-all secrets.allowed
- List your configured allowed patterns in .gitallowed at repository's root directory
- Use --no-verify if this is a one-time false positive
```
Even more interesting:
Detecting password pattern in git history:
git secrets --scan-history