HOL Guard
Open-source antivirus for AI agents: block risky tools, secret access, prompt injection, malicious packages, MCP servers, plugins, and skills at runtime.
Is HOL Guard safe? Strong public trust posture, backed by multiple independent signals.
Compare HOL Guard
How does it stack up against its Security & Guardrails neighbours?
Pick any agent to compare →In detail: HOL Guard scores 92.2/100 (Grade A), ranked #7 of 1343 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 9.6/10; 98% of recent commits are signed; no published advisory affects its latest release (hol-guard); last pushed 2026-10-01. Every point is earned from checkable signals — never paid placement. How scoring works →
How HOL Guard compares in Security & Guardrails
- #1 HOL Guard 92.2 this agent
- #2 DvalinCode 84.8 −7.4
- #3 REA 79.1 −13.1
- #4 Guardrails AI 76.5 −15.7
- #5 NeMo Guardrails 71.9 −20.3
Bars show each HVTrust score; the tick marks HOL Guard’s 92.2.
Where the 92.2 comes from
HVTrust dimensions vs the Security & Guardrails average
92.2 / 100 · 100.0% confidenceHOL Guard Security & Guardrails average (22 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 A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
76.7 / 100Supply Chain Trust
Common questions about HOL Guard
Does HOL Guard publish package provenance?
Does HOL Guard have an OpenSSF Scorecard?
Is HOL Guard actively maintained?
What license does HOL Guard use?
Are HOL Guard'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 HOL Guard 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 HOL Guard'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 HOL Guard?
For maintainers
HVTrust scores HOL Guard 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/hol-guard)
<a href="https://hvtracker.net/agents/hol-guard"><img src="https://hvtracker.net/badge/hol-guard.svg" alt="HVTrust"></a>
Other agents in Security & Guardrails
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON