Garak

the LLM vulnerability scanner

Security & Guardrails Python Grade C Listed Apache-2.0
58.7/100
Rank #338 of 1308
Compare Garak

How does it stack up against its Security & Guardrails neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade A · 4/5 signals
Last push
2026-08-21 · 4d ago
Recent change
Rank +3

Is Garak safe? Garak scores 58.7/100 (Grade C), ranked #338 of 1308 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 76% of recent commits are signed; last pushed 2026-08-21. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-25
Rank Moved
Rank rose 18 spots (#356 → #338)
2026-08-24
Rank Moved
Rank dropped 20 spots (#336 → #356)
2026-08-22
Rank Moved
Rank rose 21 spots (#353 → #332)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
86.1
Activity sub-score · out of 100
#9

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-25 06:08 UTC · Repo last pushed 4 days ago

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars
9.0k
Forks
1.2k
Last Push
2026-08-21
4 days ago
Commits (4 wk)
76
Downloads (7d)
14,434
pypi
HN mentions (30d)
0
Open Issues
237
Rank Change
▲18
was #356

Analysis

HVTrust Dimensions vs Security & Guardrails

58.7 / 100 · 100.0% confidence

Garak Security & Guardrails average (20 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.1 / 25
1.0 above avg 9.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.4 below avg 12.2
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
0.9 above avg 11.9
Maintenance60% last-push freshness · 40% commit activity
19.3 / 20
3.0 above avg 16.3
AdoptionLog-scaled stars · package downloads
15.0 / 20
5.0 above avg 10.0

Activity Inputs

86.1 / 100
StarsRepository reach
23.7 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
23.5 / 25
CommunityFork signal
14.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.0 / 10
OpenSSF Scorecard · scanned Aug 24, 2026
Signed Commits
76%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 7
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 2

Is Garak safe?

Garak has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Garak publish package provenance?
No published build provenance is currently detected for Garak. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Garak have an OpenSSF Scorecard?
Garak has an OpenSSF Scorecard score of 5.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Garak actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does Garak use?
Garak ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Garak's commits signed?
76% of the last 100 commits to Garak are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
8 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Warning
1 package source mismatch detected
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Garak's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-06-05
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo

Maintain Garak?

For maintainers

HVTrust scores Garak from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 16Score 2HVTrust 1Drift 1
2026-08-25
Rank Moved
Rank rose 18 spots (#356 → #338)
2026-08-24
Rank Moved
Rank dropped 20 spots (#336 → #356)
2026-08-22
Rank Moved
Rank rose 21 spots (#353 → #332)
2026-08-19
Rank Moved
Rank dropped 15 spots (#334 → #349)
2026-08-17
Rank Moved
Rank rose 17 spots (#353 → #336)
2026-08-13
Rank Moved
Rank dropped 24 spots (#332 → #356)
2026-08-12
Rank Moved
Rank rose 15 spots (#347 → #332)
2026-08-10
Rank Moved
Rank dropped 19 spots (#336 → #355)
2026-08-08
Rank Moved
Rank dropped 85 spots (#249 → #334)
2026-08-04
Rank Moved
Rank dropped 13 spots (#195 → #208)
2026-08-02
Rank Moved
Rank rose 10 spots (#209 → #199)
2026-07-24
Rank Moved
Rank rose 28 spots (#235 → #207)
2026-07-24
Activity Score Changed
Activity score up 8pts (79 → 88)
2026-07-21
Rank Moved
Rank rose 14 spots (#247 → #233)
2026-07-15
Rank Moved
Rank dropped 20 spots (#215 → #235)
2026-07-13
Rank Moved
Rank dropped 28 spots (#182 → #210)
2026-06-24
Rank Moved
Rank dropped 11 spots (#92 → #103)
2026-06-05
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-05-29
HVTrust Changed
HVTrust up 9.9pts (57.2 → 67.1)
2026-05-28
Activity Score Changed
Activity score up 25pts (62 → 87)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 58.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/garak.svg)](https://hvtracker.net/agents/garak)
HTML:
<a href="https://hvtracker.net/agents/garak"><img src="https://hvtracker.net/badge/garak.svg" alt="HVTrust"></a>

Other agents in Security & Guardrails

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON