https://github.com/matthewdeanmartin/find_known_secrets

Scan for known secrets in your source code before you check in
https://github.com/matthewdeanmartin/find_known_secrets

Last synced: 18 days ago
JSON representation

Scan for known secrets in your source code before you check in

• Host: GitHub
• URL: https://github.com/matthewdeanmartin/find_known_secrets
• Owner: matthewdeanmartin
• License: mit
• Created: 2018-07-11T19:56:35.000Z (over 6 years ago)
• Default Branch: main
• Last Pushed: 2023-05-29T13:48:27.000Z (over 1 year ago)
• Last Synced: 2024-11-22T15:15:47.941Z (about 2 months ago)
• Language: Python
• Size: 97.7 KB
• Stars: 6
• Watchers: 3
• Forks: 1
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • Changelog: ChangeLog
  • License: LICENSE

Awesome Lists containing this project

README

        
# find_known_secrets

Scan for known secrets in your source code before you check in

badges

------

![Libraries.io dependency status for latest release](https://img.shields.io/librariesio/release/pypi/find-known-secrets) [![Downloads](https://pepy.tech/badge/find_known_secrets/month)](https://pepy.tech/project/find-known-secrets/month)

Three Ways to Detect Secrets

----------

Pattern detection - use grep to find words like "password". git-secrets does this as well as pylint.

High entropy detection - detect-secrets does this.

Search for known secrets - Some secrets are found in conventional locations, such as AWS keys. They are typically key value pairs. As far as I known, this is a novel approach as of July 2018. So I wrote one.

All three approaches have different failure profiles.