SecretScanner
git-secrets
Our great sponsors
| SecretScanner | git-secrets | |
|---|---|---|
| 7 | 32 | |
| 2,950 | 11,982 | |
| 1.4% | 0.8% | |
| 7.3 | 1.3 | |
| 6 days ago | 16 days ago | |
| Go | Shell | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SecretScanner
-
Securing the software supply chain in the cloud
SecretScanner
-
ThreatMapper 1.3.0: Now with Secret Scanning, Runtime SBOMs, and More
In this release, we’ve integrated the open source project called SecretScanner into ThreatMapper so that now you can scan for both vulnerabilities and secrets in production, assess the risks associated across all potential issues, and then prioritize remediation accordingly.
git-secrets
-
Fired for leaked credentials. How do I explain this?
Well, this doesn't really happen at places that don't suck. They had no least privilege access to critical secrets and no processes (like pre-commit hooks using git-secrets) to prevent them being committed.
- Managing secrets like API keys in Python - Why are so many devs still hardcoding secrets?
-
Securing the software supply chain in the cloud
git-secrets
-
How to deal with unintended information leakage when using GitHub as your GIT?
Install git-secrets. Go into each of your repos, scan for past mistakes, and add a git-commit hook:
- GitHub Access Token Exposure
-
Security scanning
I agree that code scanning is really important, the best way to convince others is to identify high-risk threats in source code and present them to the decision-makers. For example, scanning Secrets is great for showing how repositories can be a massive vulnerability and identifying some low-hanging fruit, especially in the git history. Attackers are really after git repository access for this reason and there are plenty of open-source or free tools that you can use to illustrate the problem. Git-Secrets, Truffle Hog. These aren't great for a long-term commercial solution, something like GitGuardian is a better commercial tool but if the goal is just to illustrate the problem then finding some high-value secrets with free tools is a good way to convince the security personnel to invest in some solutions. Then the door is open to having more conversations as you have already proven the risk.
-
Toyota Accidently Exposed a Secret Key Publicly on GitHub for Five Years
I worked for a big startup last year and was on a contract deadline for integrating a vendor framework into a React Native app.
It was taking too long to get a new temp demo license key and GitHub search with clever filters helped me track down a demo key that was recently uploaded to a test repo.
This is also why I use git-secrets in my repos.
-
Making a GitHub repo code vulnerability/security health checker.
2) Clone the actual repo including history to look for committed secrets, running something like https://github.com/awslabs/git-secrets.
- Show HN: No Secrets Quickly find sensitive files in your GitHub repo
- Secrets: A command-line tool to prevent committing secret keys into your source
What are some alternatives?
trufflehog - Find and verify credentials
gitleaks - Protect and discover secrets using Gitleaks 🔑
secretlint - Pluggable linting tool to prevent committing credential.
shhgit - Ah shhgit! Find secrets in your code. Secrets detection for your GitHub, GitLab and Bitbucket repositories.
ThreatMapper - Open source cloud native security observability platform. Linux, K8s, AWS Fargate and more.
aws-vault - A vault for securely storing and accessing AWS credentials in development environments
SecretFinder - SecretFinder - A python script for find sensitive data (apikeys, accesstoken,jwt,..) and search anything on javascript files
semgrep - Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.
repo-supervisor - Scan your code for security misconfiguration, search for passwords and secrets. :mag:
dmca - Repository with text of DMCA takedown notices as received. GitHub does not endorse or adopt any assertion contained in the following notices. Users identified in the notices are presumed innocent until proven guilty. Additional information about our DMCA policy can be found at
PacketStreamer - :star: :star: :star: Distributed tcpdump for cloud native environments :star: :star: :star:
cariddi - Take a list of domains, crawl urls and scan for endpoints, secrets, api keys, file extensions, tokens and more