GitGuardian is described as 'Global cybersecurity startup focusing on code security solutions for the DevOps generation. A leader in the market of secrets detection and remediation, its solutions are already used by hundred thousands developers in all industries' and is an app in the security & privacy category. There are more than 10 alternatives to GitGuardian for Mac, Windows, Linux, SaaS and Web-based. The best GitGuardian alternative is AquilaX, which is free. Other great apps like GitGuardian are Vulnerabilities.io, repo-security-scanner, Cremit and AWS Lab's git-secrets.
AquilaX Ultimate is a comprehensive software security scanner, designed to detect a wide range of security vulnerabilities in the source code of any application. Is committed to change how contextual analysis is done to eliminate virtually any false positive.
A single pane of glass for understanding and mitigating risks across your entire codebase and supply chain.
CLI tool that finds secrets accidentally committed to a git repo, eg passwords, private keys - UKHomeOffice/repo-security-scanner
Cremit is an all-in-one credential security platform designed for developers and security teams. This service integrates with source code version control systems, collaboration tools, and messaging platforms to effectively detect and manage secret information.
git-secrets scans commits, commit messages, and --no-ff merges to prevent adding secrets into your git repositories. If a commit, commit message, or any commit in a --no-ff merge history matches one of your configured prohibited regular expression patterns, then the commit is...
Gitrob is a tool to help find potentially sensitive files pushed to public repositories on Github. Gitrob will clone repositories belonging to a user or organization down to a configurable depth and iterate through the commit history and flag files that match signatures for...
detect-secrets is an aptly named module for (surprise, surprise) detecting secrets within a code base.
Searches through git repositories for secrets, digging deep into commit history and branches. This is effective at finding secrets accidentally committed.
It happens sometimes that you can commit secrets or passwords to your repository by accident. The recommended best practice is not commit the secrets, that's obvious. But not always that obvious when you have a big merge waiting to be reviewed.
rules to identify files containing juicy information like usernames, passwords etc - DiabloHorn/yara4pentesters
United Kingdom
