PAGES
← all tools
◆ SAST / SCA / Code Security

graudit

v4.1 open-source

graudit is a simple script and signature sets that allows you to find potential security flaws in source code using the GNU utility grep.

Summary

graudit is an open-source command-line tool that scans source code for potential security flaws using grep and a set of signature databases, so there is no cost to run it. You point it at a path with a chosen database and it prints matches with surrounding context, making it a fit for developers or application security reviewers who want a quick check without installing a full static-analysis platform. Its README places it alongside RATS, SWAAT and flaw-finder, but distinguishes itself by keeping requirements minimal, running anywhere grep does, and covering languages from Python and Java to Ruby, PHP and dotnet, plus rulesets for Docker, JWTJWTAn open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. issues, secrets and third-party JavaScript. First committed in 2009, it remains active, with 20 contributors and 46 commits in the past year.

graudit is a simple script and signature sets that allows you to find potential security flaws in source code using the GNU utility grep.

How graudit helps

Which lines in this codebase match known-dangerous patterns for the language it's written in?

scans the path against the signature database for that language and prints each match with surrounding lines of context so you can judge it on the spot

Which of my source files are handling secrets or tokens in a way that could leak them?

runs the secrets and JWT signature sets against the tree and reports the matching lines by file, without needing the code to build or run

Are my Dockerfiles doing anything a reviewer would flag?

checks them against a dedicated ruleset for container configuration issues and prints the offending lines in place

Is this legacy or oddball codebase covered without setting up a full analysis platform?

works off plain text matching through grep, so any language with a signature database can be scanned with the same command and no build step

Which third-party JavaScript in this project has known problem patterns?

applies the third-party JavaScript ruleset to vendored or bundled scripts and lists the matching lines for review

What security-relevant code changed between two points in my repository's history?

the giterate and svnlog scripts walk git or Subversion history so matches can be traced across commits instead of only the current checkout

all 6 features, with the evidence for each →

Languages

Not documented

Features

6 capabilities across 2 capability groups

Built from graudit's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • graudit covers 1 of the 8 vulnerability assessment methods capabilities we track.
  • graudit covers 1 of the 5 supply chain security capabilities we track.

What graudit offers you

  • Command-line interface1
  • Scripting language support1
  • User-defined detection rules1
Static application security testing 4 features Vulnerability assessment methods since 2019
Grep-based source code auditing shipped Scans source code for potential vulnerabilities by matching patterns from signature databases across multiple languages and frameworks. 10 releases · 11 other sources · first seen Oct 2019

Shared capability: Static application security testing

Also counts toward: Command-line interface

release 10 total

  • Adds ios database for scanning iOS source code. v4.1 · Oct 2026 · source · release history
  • New Docker ruleset for flagging security issues in Dockerfiles and container configs. v3.9 · May 2025 · source · release history
  • New jwt ruleset for detecting JWT-related security issues in source code. v3.9 · May 2025 · source · release history
  • Updated rulesets for dotnet, Go, Java, JavaScript, PHP, Python, Ruby, Scala, SQL, and secrets detection. v3.9 · May 2025 · source · release history
  • Added basic scala rules to expand language coverage for source code analysis 2.6 · Jun 2020 · source · release history
  • Added basic support for Go language v2.4 · Mar 2020 · source · release history

docs 7 total

  • $Id: template.in.1,v 1.1 2010/06/02 12:15:32 kristaps Exp $ (C) Copyleft Eldar Wireghoul Marcussen - http://www.justanotherhacker.com. See mdoc(7) for further reference. Dd $Mdocdate : June 2 2010 $ Replace the following with the name of your utility in UPPERCASE. seen Sep 2026 · source
  • 257 .\" $Id: template.in.1,v 1.1 2010/06/02 12:15:32 kristaps Exp $ .\" (C) Copyleft Eldar Wireghoul Marcussen - http://www.justanotherhacker.com. .\" See mdoc(7) for further reference. .Dd $Mdocdate: June 2 2010 $ .\" Replace the following with the name of your utility in UPPERCASE. seen Aug 2026 · source
  • 257 $Id: template.in.1,v 1.1 2010/06/02 12:15:32 kristaps Exp $ (C) Copyleft Eldar Wireghoul Marcussen - http://www.justanotherhacker.com. See mdoc(7) for further reference. Dd $Mdocdate : June 2 2010 $ Replace the following with the name of your utility in UPPERCASE. seen Aug 2026 · source
  • 256 Find all pull requests that aren't related to any open issues with -linked:issue seen Aug 2026 · source
  • wireghoul / graudit Public Uh oh! There was an error while loading. Please reload this page . Notifications You must be signed in to change notification settings Fork 255 Star 1.7k File tree Expand file tree Collapse file tree Open diff view settings Filter options Changelog graudit misc 3partyjs.db ampscript.db… docs update · Jul 2026 · source
  • wireghoul / graudit Public Uh oh! There was an error while loading. Please reload this page . Notifications You must be signed in to change notification settings Fork 255 Star 1.7k Version 3.9 wireghoul released this 22 May 11:43 v3.9 a0ec268 This commit was created on GitHub.com and signed with GitHub’s verified… docs update · Jul 2026 · source

example

  • Scan an iOS project for known security flaws using the new iOS ruleset. graudit -d ios /path/to/ios/project v4.1 · Oct 2026 · source
  • Scan source code for Regex DoS vulnerabilities using the new ReDoS database. graudit -d misc/redos /path/to/scan v4.1 · Oct 2026 · source
  • Scan a local project directory for high-impact PHP security bugs using the new flatline script. ./misc/flatline.php /path/to/website v2.3 · Oct 2019 · source
  • Basic scan of a path graudit [opts] /path/to/scan
Secrets detection shipped Scans local project directories and remote repositories for hardcoded secrets, credentials, and interesting files. 7 releases · 3 other sources · first seen Oct 2019

Shared capability: Static application security testing

Also counts toward: User-defined detection rules, Scripting language support

release 7 total

  • Adds secrets database for detecting hardcoded secrets in source code. v4.1 · Oct 2026 · source · release history
  • New svnlog misc script for working with Subversion logs. v3.9 · May 2025 · source · release history
  • New giterate misc script for iterating over git repositories. v3.9 · May 2025 · source · release history
  • New svnscan misc script for scanning Subversion repositories. v3.9 · May 2025 · source · release history
  • Adds Eiffel language support for secret scanning via new eiffel rules v3.5 · Dec 2022 · source · release history
  • Adds TypeScript language support for secret scanning via new typescript rules v3.5 · Dec 2022 · source · release history

example

  • Scan a codebase for hardcoded secrets such as API keys and passwords. graudit -d secrets /path/to/scan v4.1 · Oct 2026 · source
  • Place custom secret detection rules in the new default path so graudit finds them without needing a manual --rules flag. mkdir -p ~/graudit/signatures && cp my_custom_rules.yaml ~/graudit/signatures/ 3.1 · Jun 2021 · source
  • Scan a remote GitHub repository for secrets and interesting files using the new graufflehog script. ./misc/graufflehog.sh https://github.com/user/repo v2.3 · Oct 2019 · source
Suppression rules documented Allows false-positive findings to be suppressed so that known-safe code patterns are excluded from scan results. 2 other sources · first seen Jul 2026

Shared capability: Static application security testing

docs

  • wireghoul / graudit Public Uh oh! There was an error while loading. Please reload this page . Notifications You must be signed in to change notification settings Fork 255 Star 1.7k Conversation EMSeek commented May 21, 2025 Copy link Copy Markdown Contributor Description More utilities, more rules Checklist All tests… docs update · Jul 2026 · source
  • wireghoul / graudit Public Uh oh! There was an error while loading. Please reload this page . Notifications You must be signed in to change notification settings Fork 255 Star 1.7k Conversation EMSeek commented Dec 19, 2025 Copy link Copy Markdown Contributor Description Updated supression rules Updated sql rules… docs update · Jul 2026 · source
Taint analysis shipped Performs data-flow taint analysis on source code (specifically C/C++) to identify potential security vulnerabilities. 1 release · 1 other source · first seen Oct 2019

Shared capability: Static application security testing

release

  • New seventaint.sh script added to the misc collection for taint-analysis workflows. v4.0 · Dec 2025 · source · release history

example

  • Perform taint analysis on C code using the new b0ftaint script. ./misc/b0ftaint.sh /path/to/source.c v2.3 · Oct 2019 · source
Dependency scanning 1 feature Supply chain security since 2022
SCA exclusion auditing shipped Audits exclusions configured in Software Composition Analysis (SCA) tools to identify potential security gaps. 1 release · first seen Jan 2022

Shared capability: Dependency scanning

release

  • Rule set for auditing SCA exclusions adds a new detection capability to audit Software Composition Analysis (SCA) tool exclusions. 3.3 · Jan 2022 · source · release history
Other / not yet classified 1 feature Features we have not matched to a capability yet. A suggested match is marked.
Vulnerability signature databases shipped suggested Ships and maintains language- and platform-specific pattern databases (e.g. JavaScript third-party libraries, AMPscript, SQL) used to identify vulnerable code patterns. 12 releases · 6 other sources · first seen Oct 2019

Suggested capability: Static application security testing. This is our guess, not confirmed.

release 12 total

  • Adds a rule linter script for validating graudit signature databases. v4.1 · Oct 2026 · source · release history
  • Adds misc/redos database for detecting Regex Denial-of-Service patterns in source code.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v4.1 · Oct 2026 · source · release history
  • Adds ruby database for scanning Ruby source code. v4.1 · Oct 2026 · source · release history
  • Adds default database used when no -d argument is supplied. v4.1 · Oct 2026 · source · release history
  • New 3partyjs ruleset in misc enables scanning for vulnerabilities in third-party JavaScript. v4.0 · Dec 2025 · source · release history
  • Updated JavaScript, PHP, Python, Golang, C, Android, Dotnet, Nim, Suppression, XSS, SQLi, Exec, Default, and Fruit rule sets for improved detection v3.6 · Apr 2024 · source · release history

docs

  • =============================================================================== =============================================================================== environment variable to the signatures directory in your .bashrc file. seen Sep 2026 · source
  • .\" (C) Copyleft Eldar "Wireghoul" Marcussen - http://www.justanotherhacker.com. .\" See mdoc(7) for further reference. .Dd $Mdocdate: June 3 2010 $ .Dt MANUALS 7 .Os .Sh NAME .Nm graudit signatures .Nd syntax and composition .Sh DESCRIPTION .Em graudit is only as good as the signature database. .Pp seen Aug 2026 · source
  • 256 (C) Copyleft Eldar Wireghoul Marcussen - http://www.justanotherhacker.com. See mdoc(7) for further reference. Dd $Mdocdate : June 3 2010 $ Dt MANUALS 7 Os Sh NAME Nm signatures Nd syntax and composition Sh DESCRIPTION Em is only as good as the signature database. Pp seen Aug 2026 · source
  • wireghoul / graudit Public Uh oh! There was an error while loading. Please reload this page . Notifications You must be signed in to change notification settings Fork 255 Star 1.7k File tree Expand file tree Collapse file tree Open diff view settings Filter options Changelog graudit misc 3partyjs.db ampscript.db… docs update · Jul 2026 · source
  • wireghoul / graudit Public Uh oh! There was an error while loading. Please reload this page . Notifications You must be signed in to change notification settings Fork 255 Star 1.7k Conversation EMSeek commented Dec 19, 2025 Copy link Copy Markdown Contributor Description Updated supression rules Updated sql rules… docs update · Jul 2026 · source

example

  • List available signature databases graudit -l

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for graudit, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail graudit puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Coverage

Missing something? Tell us

What graudit connects to, runs on and detects, read from its release notes and docs. So far: 3 new detections, 2 new supported platforms, 1 updated detection.

Show

6 changes, tracked since Oct 13, 2026.

  • Oct 132026

    new Regex DoS (ReDoS) rules

    With misc/redos

    Added misc/redos (Regex DoS) rules

    v4.1 Source ↗

  • Oct 132026

    new Secrets detection rules

    Added secrets rules

    v4.1 Source ↗

  • Oct 132026

    new iOS rules

    Added ios rules

    v4.1 Source ↗

  • Oct 132026

    new Ruby rules

    Added ruby rules

    v4.1 Source ↗

  • Oct 132026

    new Default rules

    Added default rules

    v4.1 Source ↗

  • Oct 132026

    updated Extended regex correctness updates across multiple rule databases

    Adds android, dotnet, java, js, nim, perl, php, python and 8 more. 18 in all.

    Updated android rules for extended regex correctness Updated c rules for extended regex correctness Updated dotnet rules for extended regex correctness Updated java rules for extended regex correctness Updated js rules for extended regex correctness Updated nim rules for extended regex correctness Updated perl rules for extended regex correctness Updated php rules for extended regex correctness Updated python rules for extended regex correctness Updated ruby rules for extended regex correctness Updated scala rules for extended regex correctness Updated typescript rules for extended regex correctness Updated default rules for extended regex correctness Updated exec rules for extended regex correctness Updated secrets rules for extended regex correctness Updated fruit rules for extended regex correctness Updated sql rules for extended regex correctness Updated strings rules for extended regex correctness Updated xss rules for extended regex correctness

    v4.1 Source ↗

How we count

Read from 1 of 20 release notes and docs updates we hold for graudit. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through graudit's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

20 entries

  1. October 20261
  2. September 20261
  3. July 20268
  4. December 20251
  5. May 20251
  6. April 20241
  7. December 20221
  8. March 20221
  9. January 20221
  10. June 20211
  11. June 20201
  12. March 20201
  13. October 20191
    Show
    Coverage in all entries

    20 entries

    Project health

    Issue, contributor and maintainer activity in wireghoul/graudit, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 1 ±0 vs prior 12 months
    2. Maintainers 1 +0 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed not measured of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog 0 of 27 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 0
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,689
    Issue themes, last 12 months not measured

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →