NeMo Guardrails

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

Security & Guardrails Python Listed NOASSERTION

Is NeMo Guardrails safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 7.1 / 10
Provenance None
Signed commits 100%
Last push yesterday
Compare NeMo Guardrails

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

Pick any agent to compare →
Suggest a correction

In detail: NeMo Guardrails scores 73.0/100 (Grade B), ranked #284 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 7.1/10; 100% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How NeMo Guardrails 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.

Chain of custody

Scanners check what the code says. This traces who ships NeMo Guardrails 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.

  1. Source Signed

    github.com/NVIDIA-NeMo/Guardrails, NOASSERTION, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 7.1/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection8
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 8
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 9
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 9
    Maintained 10
    Packaging 10
    Pinned-Dependencies 3
    SAST 10
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages Not linked

    • PyPI nemoguardrails Source link isn't a GitHub repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of NeMo Guardrails.

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 NeMo Guardrails’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 NeMo Guardrails compares in Security & Guardrails

  1. #4 DvalinCode 83.2 +10.2
  2. #5 Guardrails AI 76.6 +3.6
  3. #6 NeMo Guardrails 73.0 this agent
  4. #7 Garak 65.3 −7.7
  5. #8 SkillSpector 64.2 −8.8

Bars show each HVTrust score; the tick marks NeMo Guardrails’s 73.0.

Where the 73.0 comes from

HVTrust dimensions vs the Security & Guardrails average

73.0 / 100 · 100.0% confidence

NeMo Guardrails Security & Guardrails average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.9 / 25
4.2 above avg 9.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.4 below avg 12.2
Transparency50% declared license · 50% OSSF Scorecard
14.5 / 17
2.2 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
17.6 / 20
2.5 above avg 15.1
AdoptionLog-scaled stars · package downloads
16.2 / 20
6.1 above avg 10.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-05
Rank Moved
Rank rose 10 spots (#293 → #283)
2026-09-25
Rank Moved
Rank dropped 11 spots (#275 → #286)
2026-09-23
Rank Moved
Rank dropped 171 spots (#105 → #276)
Maintainer Checklist
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
79.5
Activity sub-score · out of 100
#6

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-10-10 04:09 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
7.3k
Forks
866
Last Push
2026-10-09
yesterday
Commits (4 wk)
25
Downloads (7d)
146,591
pypi
HN mentions (30d)
0
Open Issues
153
Rank Change
▲1
was #285

Analysis

Activity Inputs

79.5 / 100
StarsRepository reach
23.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
17.6 / 25
CommunityFork signal
13.7 / 20

Common questions about NeMo Guardrails

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 7.1/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
Rank 14
2026-10-05
Rank Moved
Rank rose 10 spots (#293 → #283)
2026-09-25
Rank Moved
Rank dropped 11 spots (#275 → #286)
2026-09-23
Rank Moved
Rank dropped 171 spots (#105 → #276)
2026-09-21
Rank Moved
Rank rose 167 spots (#272 → #105)
2026-09-20
Rank Moved
Rank dropped 15 spots (#257 → #272)
2026-09-16
Rank Moved
Rank rose 16 spots (#266 → #250)
2026-09-07
Rank Moved
Rank dropped 15 spots (#238 → #253)
2026-09-05
Rank Moved
Rank dropped 53 spots (#185 → #238)
2026-09-03
Rank Moved
Rank dropped 12 spots (#166 → #178)
2026-08-31
Rank Moved
Rank dropped 17 spots (#143 → #160)
2026-08-26
Rank Moved
Rank dropped 13 spots (#118 → #131)
2026-08-17
Rank Moved
Rank rose 12 spots (#128 → #116)
2026-08-08
Rank Moved
Rank dropped 14 spots (#99 → #113)
2026-07-13
Rank Moved
Rank dropped 10 spots (#77 → #87)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 73.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.4 · Raw JSON