Garak
the LLM vulnerability scanner
Is Garak safe? Promising trust profile, but some evidence still deserves review.
Compare Garak
How does it stack up against its Security & Guardrails neighbours?
Pick any agent to compare →In detail: Garak scores 65.6/100 (Grade B), ranked #468 of 1371 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 4.7/10; 71% of recent commits are signed; no published advisory affects its latest release (garak); last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →
How Garak could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.6 → 80.2 A · #4 of 26
- Raise the OSSF Scorecard from 4.7 to 9.0lowest checks: CII-Best-Practices 0, Dependency-Update-Tool 0, Fuzzing 0 +9.0 → 74.6 B · #5 of 26
- Sign every commit71% signed today +1.5 → 67.1 B · #6 of 26
Chain of custody
Scanners check what the code says. This traces who ships Garak and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/NVIDIA/garak, Apache-2.0, last pushed 2026-10-08. 71% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.7/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:
- Code Review5
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 10CII-Best-Practices 0Code-Review 5Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 10Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages Linked, not attested
- PyPI garak Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: garak 0.17.0. No published advisory affects it (OSV, checked 2026-10-09).
Changes to this chain
- 2026-10-02 Provenance drift warning cleared (now: unknown)
Evidence behind this score
Coverage A: 4 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Garak’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Garak compares in Security & Guardrails
- #4 Guardrails AI 76.7 +11.1
- #5 NeMo Guardrails 73.0 +7.4
- #6 Garak 65.6 this agent
- #7 SkillSpector 64.2 −1.4
- #8 Snyk Agent Scan 63.9 −1.7
Bars show each HVTrust score; the tick marks Garak’s 65.6.
Where the 65.6 comes from
HVTrust dimensions vs the Security & Guardrails average
65.6 / 100 · 100.0% confidenceGarak Security & Guardrails average (26 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
83.6 / 100Common questions about Garak
Does Garak publish package provenance?
Does Garak have an OpenSSF Scorecard?
Is Garak actively maintained?
What license does Garak use?
Are Garak's commits signed?
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.
Compare Garak head-to-head
AI agent surface
MCP, providers, tool surface
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/garak)
<a href="https://hvtracker.net/agents/garak"><img src="https://hvtracker.net/badge/garak.svg" alt="HVTrust"></a>
Other agents in Security & Guardrails
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.4 · Raw JSON