An enterprise friendly way of detecting and preventing secrets in code
detect-secrets is an aptly named module for (surprise, surprise) detecting secrets within a code base.
However, unlike other similar packages that solely focus on finding secrets, this package is designed with the enterprise client in mind: providing a backwards compatible, systematic means of:
Preventing new secrets from entering the code base,
Detecting if such preventions are explicitly bypassed, and
Providing a checklist of secrets to roll, and migrate off to a more secure storage.
This way, you create a separation of concern: accepting that there may currently be secrets hiding in your large repository (this is what we refer to as a baseline), but preventing this issue from getting any larger, without dealing with the potentially gargantuan effort of moving existing secrets away.
It does this by running periodic diff outputs against heuristically crafted regex statements, to identify whether any new secret has been committed. This way, it avoids the overhead of digging through all git history, as well as the need to scan the entire repository every time.
For a look at recent changes, please see CHANGELOG.md.
If you are looking to contribute, please see CONTRIBUTING.md.
For more detailed documentation, check out our other documentation.
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:ojkastl_buildservice:Branch_security/python-detect-secrets && cd $_ - Create Badge
Source Files
| Filename | Size | Changed |
|---|---|---|
| detect_secrets-1.5.0.tar.gz | 0000097351 95.1 KB | |
| python-detect-secrets.changes | 0000000260 260 Bytes | |
| python-detect-secrets.spec | 0000002232 2.18 KB |
Comments 0