git-secrets
snyk
git-secrets | snyk | |
---|---|---|
32 | 63 | |
12,026 | 4,065 | |
0.6% | - | |
1.0 | 9.9 | |
20 days ago | over 1 year ago | |
Shell | TypeScript | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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.
-
Recovering from Accidentally Pushing Sensitive Information to a Remote Git Repository
# macOS brew install git-secrets # Linux git clone https://github.com/awslabs/git-secrets.git cd git-secrets make install
- Managing secrets like API keys in Python - Why are so many devs still hardcoding secrets?
-
If you pay for an API key depending on the amount of requests, is it safe to push your code to GitHub?
You could use Git hooks to prevent someone from being able to author a commit when you suspect there is a secret being committed. In addition to this, you could also perform this check server-side, in case someone did not run their Git hooks for whatever reason. For example, check out git-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.
https://github.com/awslabs/git-secrets
-
Marking findings as FPs in recurring scans
Under the covers, it is simply looking up an 'ignore' list stored in YML during each scan. If you are building your own, you might also want to see how AWS Labs is doing it in their solution git secrets.
snyk
-
Snyk CLI: Introducing Semantic Versioning and release channels
Snyk CLI was introduced to the World Wide Web and security enthusiasts on October 2, 2015, as v0.0.0-pre-alpha release. In the past eight years, we released Snyk CLI nearly two thousand times — and more than eleven hundred of those releases happened in the last three years. That’s one release every thirty-two hours, signifying our customers’ growing needs as well as the pace at which we operate to meet those needs at an enterprise scale. With increasing demand, the complexity, reach, and impact of our fast-paced code changes increased, too.
-
How to secure JavaScript applications right from the CLI
There are a number of ways that you can install the Snyk CLI on your machine, ranging from using the available stand-alone executables to using package managers such as Homebrew for macOS and Scoop for Windows.
-
Axios shipped a buggy version and it broke many productions apps. Let this be a lesson to pin your dependencies!
There's tons of tools to solve each of these problems Snyk for vulnerability scanning, tons of license checker plugins (like we use license-webpack-plugin which generates the license text for everything we distribute and fails a build if a license doesn't have one of our allowlisted licenses.
-
The US military wants to understand the most important software on Earth - Open-source code runs on every computer on the planet—and keeps America’s critical infrastructure going. DARPA is worried about how well it can be trusted
oh, such companies already exist: For example Snyk
-
Badges - TL;DR for your repository's README
Snyk provides security score and vulnerability count badges, which you can link to the relevant pages, as in these examples:
-
If you had a few days to improve an existing Rails project before going live - what would you focus on?
If you app is dockerized I would recommend adding something like Snyk to make sure your image is safe.
-
NodeSecure CLI v2.0.0
Note: I remind you that we support multiple strategy for vulnerabilities like Sonatype or Snyk.
-
Free project-leading mentorship for senior engineers
My name is Adam, and I am a software engineer working at Snyk for the past 2.5 years. Over the past year, I have been leading a few projects that spanned multiple teams. My colleague is a tech lead at Snyk, and he’s been coaching people on how to lead projects effectively for a few years now.
-
What should I expect from a MacOS development environment in enterprise?
So I'm curious, how are businesses building iOS apps securely? Could a tool like Snyk replace a manual audit, or is it a good idea to have an initial manual audit of our desired environment?
-
RFC: A Full-stack Analytics Platform Architecture
Ideally, software can quickly go from development to production. Continuous deployment and delivery are some processes that make this possible. Continuous deployment means establishing an automated pipeline from development to production while continuous delivery means maintaining the main branch in a deployable state so that a deployment can be requested at any time. Predecos uses these tools. When a commit goes into master, the code is pushed directly to the public environment. Deployment also occurs when a push is made to a development branch enabling local/e2e testing before push to master. In this manner the master branch can be kept clean and ready for deployment most of the time. Problems that surface resulting from changes are visible before reaching master. Additional automated tools are used. Docker images are built for each microservice on commit to a development or master branch, a static code analysis is performed by SonarCloud revealing quality and security problems, Snyk provides vulnerability analysis and CodeClimate provides feedback on code quality while Coveralls provides test coverage. Finally, a CircleCI build is done. Each of these components use badges which give a heads-up display of the health of the system being developed. Incorporating each of these tools into the development process will keep the code on a trajectory of stability. For example, eliminating code smells, security vulnerabilities, and broken tests before merging a pull-request (PR) into master. Using Husky on development machines to ensure that code is well linted and locally tested before it is allowed to be pushed to source-control management (SCM). Applying additional processes such as writing tests around bugs meaning reintroduction of a given bug would cause a test to fail. The automated tools would then require that test to be fixed before push to SCM meaning fewer bugs will be reintroduced. Proper development processes and automation have a strong synergy.
What are some alternatives?
trufflehog - Find and verify secrets
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
gitleaks - Protect and discover secrets using Gitleaks 🔑
semgrep - Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.
secretlint - Pluggable linting tool to prevent committing credential.
SonarQube - Continuous Inspection
shhgit - Ah shhgit! Find secrets in your code. Secrets detection for your GitHub, GitLab and Bitbucket repositories.
renovate
aws-vault - A vault for securely storing and accessing AWS credentials in development environments
nsp
SecretFinder - SecretFinder - A python script for find sensitive data (apikeys, accesstoken,jwt,..) and search anything on javascript files
Themis - Easy to use cryptographic framework for data protection: secure messaging with forward secrecy and secure data storage. Has unified APIs across 14 platforms.