NeMo Guardrails

NeMo Guardrails is an open-source toolkit for easily adding programmable guardrails to LLM-based conversational systems.

Security & Guardrails Python Grade B Listed NOASSERTION
72.0/100
Rank #117 of 1283
Compare NeMo Guardrails

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-11 · 0d ago
Recent change
Rank

Is NeMo Guardrails safe? NeMo Guardrails scores 72.0/100 (Grade B), ranked #117 of 1283 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 6.4/10; 100% of recent commits are signed; last pushed 2026-08-11. 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-08
Rank Moved
Rank dropped 14 spots (#99 → #113)
2026-07-13
Rank Moved
Rank dropped 10 spots (#77 → #87)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.4/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.
82.2
Activity sub-score · out of 100
#3

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 →

Signals refreshed 2026-08-11 20:02 UTC · Repo last pushed today

Activity & Reach

Stars
6.9k
Forks
804
Last Push
2026-08-11
today
Commits (4 wk)
45
Downloads (7d)
79,331
pypi
HN mentions (30d)
0
Open Issues
130
Rank Change
=
was #117

Analysis

HVTrust Dimensions vs Security & Guardrails

72.0 / 100 · 100.0% confidence

NeMo Guardrails Security & Guardrails average (19 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.0 / 25
4.7 above avg 8.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.1 below avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
13.9 / 17
2.2 above avg 11.7
Maintenance60% last-push freshness · 40% commit activity
18.6 / 20
2.2 above avg 16.4
AdoptionLog-scaled stars · package downloads
15.7 / 20
5.7 above avg 10.0

Activity Inputs

82.2 / 100
StarsRepository reach
23.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
20.7 / 25
CommunityFork signal
13.5 / 20

Supply Chain Trust

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

Is NeMo Guardrails safe?

NeMo Guardrails 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 NeMo Guardrails publish package provenance?
No published build provenance is currently detected for NeMo Guardrails. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does NeMo Guardrails have an OpenSSF Scorecard?
NeMo Guardrails has an OpenSSF Scorecard score of 6.4/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 NeMo Guardrails actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does NeMo Guardrails use?
NeMo Guardrails ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are NeMo Guardrails's commits signed?
100% of the last 100 commits to NeMo Guardrails 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.

Compare NeMo Guardrails head-to-head

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
1 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
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain NeMo Guardrails?

For maintainers

HVTrust scores NeMo Guardrails 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
HVTrust 2Rank 2Listed 1Grade 1Scorecard 1Score 1
2026-08-08
Rank Moved
Rank dropped 14 spots (#99 → #113)
2026-07-13
Rank Moved
Rank dropped 10 spots (#77 → #87)
2026-05-29
HVTrust Changed
HVTrust up 10.0pts (62.1 → 72.1)
2026-05-28
Activity Score Changed
Activity score up 23pts (61 → 84)
2026-05-27
Scorecard Added
OSSF Scorecard: 6.8/10
2026-05-27
Grade Changed
Trust grade D → B
2026-05-27
HVTrust Changed
HVTrust up 41.6pts (25.1 → 66.7)
2026-05-25
Newly Listed
First tracked at rank #108

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 72.0 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/nemo-guardrails.svg)](https://hvtracker.net/agents/nemo-guardrails)
HTML:
<a href="https://hvtracker.net/agents/nemo-guardrails"><img src="https://hvtracker.net/badge/nemo-guardrails.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