Is Llama Guard safe to use?

Llama Guard has an HVTrust score of 52.9/100 (Grade C), ranked #416 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Llama Guard?

Llama Guard scores 52.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 4.3k GitHub stars and is categorized under Security & Guardrails.

Llama Guard

meta-llama/PurpleLlama

Set of tools to assess and improve LLM security.

Security & Guardrails Python Grade C Listed NOASSERTION

52.9/100

Rank #416 of 1204

Compare Llama Guard

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-06 · 3d ago

Recent change

Rank

Is Llama Guard safe? Llama Guard scores 52.9/100 (Grade C), ranked #416 of 1204 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.8/10; 1% of recent commits are signed; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

#8 PentestAgent — 57.0 (C) → #9 LLM Guard — 55.4 (C) → #11 Agentic Security — 49.7 (D) → #12 HexStrike AI — 45.9 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 104 spots (#311 → #415)

2026-07-15

Rank Moved

Rank dropped 20 spots (#272 → #292)

2026-07-14

Rank Moved

Rank dropped 14 spots (#258 → #272)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.8/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Llama Guard View Security & Guardrails Report missing data

68.5

Activity sub-score · out of 100

#10

In Security & Guardrails

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 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 →

Activity & Reach

Stars

4.3k

Forks

766

Last Push

2026-08-06

3 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

Open Issues

Rank Change

▼1

was #415

Analysis

HVTrust Dimensions vs Security & Guardrails

52.9 / 100 · 100.0% confidence

Llama Guard Security & Guardrails average (17 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.3 / 25

in line with avg 7.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 11.2

Transparency50% declared license · 50% OSSF Scorecard

13.4 / 17

1.7 above avg 11.7

Maintenance60% last-push freshness · 40% commit activity

13.2 / 20

2.9 below avg 16.1

AdoptionLog-scaled stars · package downloads

8.7 / 20

1.5 below avg 10.2

Activity Inputs

68.5 / 100

StarsRepository reach

21.8 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

8.7 / 25

CommunityFork signal

13.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.8 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests -1

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 10

License 9

Maintained 9

Packaging -1

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Llama Guard safe?

Public trust evidence for Llama Guard is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Llama Guard publish package provenance?

No published build provenance is currently detected for Llama Guard. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Llama Guard have an OpenSSF Scorecard?

Llama Guard has an OpenSSF Scorecard score of 5.8/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 Llama Guard actively maintained?

Actively maintained. The repository was pushed to within the last 3 day(s).

What license does Llama Guard use?

Llama Guard ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Llama Guard's commits signed?

1% of the last 100 commits to Llama Guard 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

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 Llama 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.

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, OpenAI

Maintain Llama Guard?

For maintainers

HVTrust scores Llama 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-08

Rank Moved

Rank dropped 104 spots (#311 → #415)

2026-07-15

Rank Moved

Rank dropped 20 spots (#272 → #292)

2026-07-14

Rank Moved

Rank dropped 14 spots (#258 → #272)

2026-07-13

Rank Moved

Rank dropped 31 spots (#227 → #258)

2026-06-24

Rank Moved

Rank dropped 27 spots (#191 → #218)

2026-06-23

Rank Moved

Rank dropped 14 spots (#177 → #191)

2026-06-18

Rank Moved

Rank dropped 14 spots (#145 → #159)

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, OpenAI

2026-06-01

Rank Moved

Rank dropped 17 spots (#103 → #120)

2026-05-29

HVTrust Changed

HVTrust up 9.8pts (47.3 → 57.1)

2026-05-28

Activity Score Changed

Activity score up 14pts (59 → 74)

2026-05-27

HVTrust Changed

HVTrust up 6.7pts (40.5 → 47.2)

2026-05-25

Newly Listed

First tracked at rank #111

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/llama-guard.svg)](https://hvtracker.net/agents/llama-guard)
            
HTML:
            <a href="https://hvtracker.net/agents/llama-guard"><img src="https://hvtracker.net/badge/llama-guard.svg" alt="HVTrust"></a>

Other agents in Security & Guardrails

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