graudit
v4.1 open-sourceThe section your link pointed to isn't on graudit's page any more, so we've brought you to the top.
graudit is a simple script and signature sets that allows you to find potential security flaws in source code using the GNU utility grep.
graudit -d secrets /path/to/scan graudit -d ios /path/to/ios/project graudit -d misc/redos /path/to/scan misc/giterate.sh secrets feature-branch misc/svnumerate.sh secrets . graudit -d docker Dockerfile bash misc/seventaint.sh /path/to/php/project graudit -d misc/3partyjs.db /path/to/js/project bash misc/seventaint.sh /path/to/php/project graudit -d misc/3partyjs.db /path/to/js/project mkdir -p ~/graudit/signatures && cp my_custom_rules.yaml ~/graudit/signatures/ ./misc/flatline.php /path/to/website ./misc/graufflehog.sh https://github.com/user/repo ./misc/b0ftaint.sh /path/to/source.c
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
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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…
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.
6 changes, tracked since Oct 13, 2026.
-
Oct 132026
new Regex DoS (ReDoS) rules
With misc/redos
Added misc/redos (Regex DoS) rules
-
Oct 132026
new Secrets detection rules
Added secrets rules
-
Oct 132026
new iOS rules
Added ios rules
-
Oct 132026
new Ruby rules
Added ruby rules
-
Oct 132026
new Default rules
Added default rules
-
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
Operating systems 1
Languages & runtimes 1
Nothing first seen in this window. That doesn't mean graudit shipped nothing, only that we found no record of it.
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
20 entries
No entries match these filters.
- October 20261
- September 20261
- July 20268
- December 20251
- May 20251
- April 20241
- December 20221
- March 20221
- January 20221
- June 20211
- June 20201
- March 20201
- October 20191
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.
- Contributors 1 ±0 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 0 of 27 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 0
- Commits / month 0
- Stars 1,689
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.