yara4pentesters Alternatives

    yara4pentesters is described as 'rules to identify files containing juicy information like usernames, passwords etc' and is an app in the Development category. There are eight alternatives to yara4pentesters for Mac, Windows, Linux, Self-Hosted solutions and SaaS. The best alternative is AWS Lab's git-secrets, which is both free and Open Source. Other great apps like yara4pentesters are Gitleaks (Free, Open Source), Gitrob (Free, Open Source), repo-security-scanner (Free, Open Source) and truffleHog (Free, Open Source).

    This page was last updated Apr 25, 2019

    1. git-secrets scans commits, commit messages, and --no-ff merges to prevent adding secrets into your git repositories.
      No screenshots yet
      • FreeOpen Source
      • Mac
      • Windows
      • Linux
      Audit git repos for secrets. Gitleaks provides a way for you to find unencrypted secrets and other unwanted data types in git source code repositories.


      • FreeOpen Source
      • Mac
      • Windows
      • Linux
      Gitrob is a tool to help find potentially sensitive files pushed to public repositories on Github.
    2. CLI tool that finds secrets accidentally committed to a git repo, eg passwords, private keys.
      • FreeOpen Source
      • Mac
      • Windows
      • Linux
      Searches through git repositories for secrets, digging deep into commit history and branches. This is effective at finding secrets accidentally committed.


    3. detect-secrets is an aptly named module for (surprise, surprise) detecting secrets within a code base.
      • Free PersonalProprietary
      • Self-Hosted
      • Software as a Service (SaaS)
      GitGuardian is a cybersecurity startup solving the issue of secrets sprawling through source code, a widespread problem that leads to some credentials ending up in compromised places or even in the public space.
      • FreeOpen Source
      • Mac
      • Windows
      • Linux
      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.
    Showing 8 of 8 alternatives