PAGES
← all tools
◆ AI Runtime Defense & Guardrails

NeMo Guardrails

v0.24.0 open-source

NeMo Guardrails is an open-source toolkit for easily adding programmable guardrails to LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code.-based conversational systems.

Summary

NeMo Guardrails is an open-source Python library, licensed under Apache 2.0, that adds programmable guardrails to LLM-based conversational applications to control outputs and block unsafe behavior. It's imported directly into an application's code, though it can also run as a standalone HTTP server exposing an OpenAI-compatible endpoint for checking inputs or outputs without generating a model response. It's built for developers building LLM applications who need to validate tool calls, screen retrieved content for context bloat, or detect and mask PIIPIIPersonally Identifiable Information — data that can identify a specific individual, such as names, email addresses, or SSNs. Cyber tools flag or redact it to limit exposure and meet privacy regulations., using either local Hugging Face classifiers or integrations like Polygraf, rather than for security teams auditing systems after the fact. It sits in the LLM runtime-protection category, alongside the broader set of guardrail and content-filtering libraries developers reach for when wiring safety checks into a chat pipeline.

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

How NeMo Guardrails helps

Is a model about to act on a tool call it was never supposed to make?

checks streaming and non-streaming tool calls locally before execution, validating both what the model emits and what the application returns, and blocks or transforms the call under the same allow/block/transform contract

Is a chunk of retrieved content going to blow up my context window?

flags oversized, repetitive, low-entropy, or padded input and retrieved text before it gets passed to the model

Is there PII sitting in a user message or a model response before it goes further?

runs local Hugging Face classifiers or a Polygraf integration across input, output, and retrieval to detect and mask it in place

Can I screen a message for safety without paying for a full model response?

sends it to a standalone endpoint that runs the configured input or output rails and returns passed, modified, or blocked without generating a completion

Did last night's policy or model change quietly loosen what gets blocked?

every rail returns the same engine-neutral allow, block, or transform outcome, so swapping configurations or engines can be compared against the same verdict contract

Which of my safety checks can run purely on request and response content, without touching my application's internal state?

typed rail manifests declare each built-in rail's configuration, actions, and privacy properties, letting the standalone checking surface execute the ones that only need message content

all 30 features, with the evidence for each →

Languages

Not documented

Features

30 capabilities across 5 areas

Built from NeMo Guardrails's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What NeMo Guardrails offers you

  • ML-based detection2
  • Command-line interface1
  • REST API1
  • Scripting language support1
Content Inspection and Filtering Rails 4 capabilities This is the core purpose of NeMo Guardrails: applying configurable checks to what goes into and comes out of an LLM. Rails can block, modify, or pass content based on policy, and can be run independently of model generation.
Standalone rail checks shipped Runs input or output checks on their own, returning a clear pass, modify, or block decision without needing a full model generation cycle. 15 releases · 3 other sources · first seen Feb 2025

Also counts toward: REST API

release 15 total

  • Adds typed rail manifests so built-in rails declare their configuration, actions, execution surfaces, requirements, and privacy properties for automatic discovery by both engines. v0.24.0 · Aug 2026 · source · release history
  • Adds a canonical outbound HTTP client shared by all built-in integrations, providing connection pooling, retries, TLS, error handling, lifecycle management, and privacy-safe tracing and metrics. v0.24.0 · Aug 2026 · source · release history
  • /v1/checks no longer accepts inline configuration; select a server-loaded configuration using config_id or rely on the server default. v0.24.0 · Aug 2026 · source · release history
  • Adds a canonical outbound HTTP client with connection pooling, retries, TLS, error handling, lifecycle management, and privacy-safe tracing and metrics for all built-in integrations. v0.24.0 · Aug 2026 · source · release history
  • Adds output-rail checking mode to the /v1/checks endpoint, which now selects a server-loaded configuration via config_id or the server default. v0.24.0 · Aug 2026 · source · release history
  • /v1/checks no longer accepts inline configuration; select a server-loaded configuration via config_id or rely on the server default. v0.24.0 · Aug 2026 · source · release history

docs

  • Open-source toolkit for adding programmable guardrails to LLM-based conversational applications to control output, enforce dialog flows, and prevent jailbreaks.

example

  • Run output-rail checks against a server-loaded config by supplying config_id to /v1/checks. curl -s -X POST http://localhost:8000/v1/checks \ -H 'Content-Type: application/json' \ -d '{"config_id": "my-guardrails-config", "messages": [{"role": "assistant", "content": "Here is the… v0.24.0 · Aug 2026 · source
  • Start a guardrails HTTP server nemoguardrails server [--config PATH/TO/CONFIGS] [--port PORT]
Tool call validation rails shipped Checks that tool calls the model emits and results returned by the application are valid, supporting both streaming and non-streaming flows. 9 releases · first seen Oct 2025

release 9 total

  • Adds multiple namespaced self-check rails with per-rail namespaced task prompts, enabling more than one self-check rail to run in the same configuration. v0.24.0 · Aug 2026 · source · release history
  • Supports running multiple self-check rails simultaneously with per-rail namespaced task prompts. v0.24.0 · Aug 2026 · source · release history
  • Run multiple self-check rails with per-rail namespaced task prompts v0.24.0 · Aug 2026 · source · release history
  • Add streaming and non-streaming tool calling support in IORails, including local rails that validate model-emitted tool calls and application-returned tool results v0.23.0 · Jul 2026 · source · release history
  • Add OpenAI-compatible tool calling parameters and response handling in the server v0.23.0 · Jul 2026 · source · release history
  • Adds streaming and non-streaming tool calling to IORails, with local rails that validate model-emitted tool calls and application-returned tool results. v0.23.0 · Jul 2026 · source · release history
Hugging Face classifier rails shipped Uses lightweight local classifier models to screen inputs, outputs, or retrieved content for unwanted categories. 3 releases · first seen Jul 2026

release

  • The hf-classifier install extra is removed; install transformers and torch directly to use the local classifier backend. v0.24.0 · Aug 2026 · source · release history
  • Adds lightweight Hugging Face classifier rails for input, output, and retrieval, backed by local Transformers, vLLM, KServe, and FMS. v0.23.0 · Jul 2026 · source · release history
  • Add lightweight Hugging Face classifier rails for input, output, and retrieval, with local Transformers, vLLM, KServe, and FMS backends v0.23.0 · Jul 2026 · source · release history
Context bloat detection rails shipped Detects oversized, repetitive, or padded content in inputs and retrieved context before it reaches the model. 2 releases · first seen Jul 2026

release

  • Add context bloat detection for oversized, repetitive, low-entropy, or padded input and retrieved content v0.23.0 · Jul 2026 · source · release history
  • Adds context bloat detection rails to flag oversized, repetitive, low-entropy, or padded input and retrieved content. v0.23.0 · Jul 2026 · source · release history
Privacy and PII Protection 1 capability NeMo Guardrails can identify and obscure personally identifiable information before it travels through the pipeline. This applies to user inputs, model outputs, and content retrieved from external sources.
PII detection and masking rails shipped Detects and masks personally identifiable information in inputs, outputs, and retrieved content using a Polygraf integration. 3 releases · 1 other source · first seen Dec 2023

release

  • Adds Polygraf integration for PII detection and masking across input, output, and retrieval rails. v0.23.0 · Jul 2026 · source · release history
  • Add Polygraf PII detection and masking for input, output, and retrieval rails v0.23.0 · Jul 2026 · source · release history
  • Adds Presidio integration for sensitive data detection guardrails v0.6.0 · Dec 2023 · source · release history

example

  • Apply Polygraf PII detection and masking to user input before it reaches the LLM. rails: input: flows: - polygraf pii detection - polygraf pii masking v0.23.0 · Jul 2026 · source
Observability and Monitoring 1 capability The tool emits structured telemetry so operators can see exactly how rails are behaving in production. Spans cover the full request lifecycle including token usage and, optionally, the content itself.
OpenTelemetry observability for rails shipped Emits OpenTelemetry spans for every rail execution, capturing request and response attributes and token usage, with optional content recording. 8 releases · first seen Mar 2025

release 8 total

  • Adds shared model telemetry and an instrumented model decorator for LLM call observability. v0.24.0 · Aug 2026 · source · release history
  • Extends IORails OpenTelemetry support with opt-in content capture and richer request, response, and token-usage span attributes. v0.23.0 · Jul 2026 · source · release history
  • Add opt-in OpenTelemetry content capture, request and response attributes, token usage, and span reference documentation v0.23.0 · Jul 2026 · source · release history
  • IORails OpenTelemetry tracing and token-level metrics integration v0.22.0 · May 2026 · source · release history
  • Enhances the tracing system to use OpenTelemetry semantic conventions for GenAI applications v0.16.0 · Sep 2025 · source · release history
  • Update tracing to use otel api v0.15.0 · Aug 2025 · source · release history
Integrations and Ecosystem Compatibility 2 capabilities NeMo Guardrails connects to common LLM frameworks and retrieval infrastructure so guardrails can be added without rebuilding existing pipelines. This includes framework-level integrations and the underlying search mechanism used by rails.
LangChain integration shipped Integrates with LangChain, including the OpenAI Responses API and Harmony response format models, so existing chains can be wrapped with rails. 9 releases · 1 other source · first seen Jan 2024

release 9 total

  • LangChain integration adds support for the OpenAI Responses API and Harmony response format models. v0.23.0 · Jul 2026 · source · release history
  • NEMOGUARDRAILS_LLM_FRAMEWORK=langchain environment variable to re-enable LangChain when using non-OpenAI providers v0.22.0 · May 2026 · source · release history
  • GuardrailsMiddleware added for seamless LangChain agent integration v0.21.0 · Mar 2026 · source · release history
  • langchain v1 compatibility is now supported in NeMo Guardrails. v0.19.0 · Dec 2025 · source · release history
  • Adds llm provider support for LangChain 1.x content blocks to handle reasoning traces and tool calls. v0.19.0 · Dec 2025 · source · release history
  • Adds automatic provider inference for LangChain LLMs v0.18.0 · Nov 2025 · source · release history

example

  • Integrate NeMo Guardrails directly into a LangChain RunnableSequence or LCEL pipeline using the new wrapper. guardrail_chain = RunnableRails(config_path).with_config(run_name="nemo_guardrails") v0.7.0 · Jan 2024 · source
Embedding similarity search shipped Provides embedding-based similarity search using a NumPy index by default, removing the need for a native C++ dependency. 3 releases · first seen Jul 2024

release

  • Replace Annoy with exact NumPy search as the default embedding index, removing the native C++ dependency while preserving existing similarity-threshold semantics v0.23.0 · Jul 2026 · source · release history
  • Replaces Annoy with exact NumPy search as the default embedding index, removing the native C++ dependency while preserving similarity-threshold semantics. v0.23.0 · Jul 2026 · source · release history
  • Enables registering and using custom embedding models via new library APIs v0.9.1 · Jul 2024 · source · release history
Other 22 capabilities
Streaming output rail execution shipped Enables the execution of output rails on streaming chunks as they are generated, rather than waiting for the full response. 12 releases · first seen Mar 2024

Also counts toward: ML-based detection

release 12 total

  • Expands IORails to execute 59 of the library's 67 action-backed input and output surfaces, including community integrations and content-transforming rails, sharing implementations with LLMRails. v0.24.0 · Aug 2026 · source · release history
  • IORails generate() and generate_async() calls that supply generation options now return GenerationResponse; message lists must be passed with messages= as a keyword argument rather than positionally. v0.24.0 · Aug 2026 · source · release history
  • The hf-classifier install extra is removed; install transformers and torch directly for the local classifier backend. v0.24.0 · Aug 2026 · source · release history
  • IORails now returns GenerationResponse from non-streaming generate() and generate_async() calls when generation options are supplied. v0.24.0 · Aug 2026 · source · release history
  • Custom actions using @action(output_mapping=...) must remove that argument and return an explicit RailOutcome from the action v0.24.0 · Aug 2026 · source · release history
  • Custom actions using @action(output_mapping=...) must remove that argument and return an explicit RailOutcome instead. v0.24.0 · Aug 2026 · source · release history
ActiveFence ActiveScore integration shipped Applies ActiveFence ActiveScore API as an input rail to evaluate content safety. 9 releases · first seen Dec 2023

release 9 total

  • Adds F5 Guardrails integration to the built-in rail library. v0.24.0 · Aug 2026 · source · release history
  • CrowdStrike AIDR community integration for rail-based moderation v0.21.0 · Mar 2026 · source · release history
  • PolicyAI integration for content moderation v0.21.0 · Mar 2026 · source · release history
  • JailbreakDetect connector: new integration for the NVIDIA NemoGuard jailbreak detection NIM microservice to identify jailbreak attempts. v0.11.1 · Jan 2025 · source · release history
  • Adds GCP moderation support v0.10.0 · Sep 2024 · source · release history
  • Adds a ContentSafetyModule to integrate content safety models v0.10.0 · Sep 2024 · source · release history
Parallel and asynchronous flow execution shipped Enables parallel flow execution for simultaneous processing and an asynchronous action execution model for non-blocking operations. 7 releases · first seen May 2024

release 7 total

  • Speculative generation in IORails that runs input rails in parallel with the main LLM response to hide latency v0.22.0 · May 2026 · source · release history
  • IORails, a new optimized Input/Output rail engine supporting parallel execution of content-safety, topic-safety, and jailbreak detection rails with logging and unique request IDs v0.21.0 · Mar 2026 · source · release history
  • RunnableRails has been rewritten to support the full LangChain Runnable protocol (sync, async, streaming, batch). v0.17.0 · Oct 2025 · source · release history
  • Support external async token generators v0.15.0 · Aug 2025 · source · release history
  • Implement parallel streaming output rails execution v0.15.0 · Aug 2025 · source · release history
  • Support parallel rails execution v0.15.0 · Aug 2025 · source · release history
IORails execution support shipped Executes action-backed input and output surfaces in IORails, sharing implementations with LLMRails. 5 releases · first seen Aug 2026

release

  • Expands IORails to execute 59 of the library's 67 action-backed input and output surfaces, including community integrations and content-transforming rails, sharing implementations with LLMRails. v0.24.0 · Aug 2026 · source · release history
  • Execute blocking rail outcomes directly in IORails via the new RailOutcome allow/block/transform contract v0.24.0 · Aug 2026 · source · release history
  • Adds RailOutcome — an engine-neutral allow, block, or transform contract returned by rail actions and enforced by both LLMRails and IORails. v0.24.0 · Aug 2026 · source · release history
  • Expands IORails to execute 59 of the library's 67 action-backed input and output surfaces, including community integrations and content-transforming rails, sharing the same rail implementations as LLMRails. v0.24.0 · Aug 2026 · source · release history
  • Adds message checks to IORails. v0.24.0 · Aug 2026 · source · release history
AlignScore fact-checking shipped Uses AlignScore for fast verification of LLM response accuracy against source content. 5 releases · first seen Dec 2023

release

Community moderation integrations shipped Adds community-contributed rail-based moderation capabilities. 4 releases · first seen Mar 2026

release

  • Adds F5 Guardrails integration to the built-in rail library. v0.24.0 · Aug 2026 · source · release history
  • Adds F5 Guardrails integration as a new built-in library rail. v0.24.0 · Aug 2026 · source · release history
  • CrowdStrike AIDR community integration for rail-based moderation v0.21.0 · Mar 2026 · source · release history
  • PolicyAI integration for content moderation v0.21.0 · Mar 2026 · source · release history
Generation response typing shipped Standardizes return types for generate() calls and enforces keyword argument usage for message lists in IORails. 4 releases · first seen Aug 2026

release

  • IORails generate() and generate_async() calls that supply generation options now return GenerationResponse; message lists must be passed with messages= as a keyword argument rather than positionally. v0.24.0 · Aug 2026 · source · release history
  • IORails now returns GenerationResponse from non-streaming generate() and generate_async() calls when generation options are supplied. v0.24.0 · Aug 2026 · source · release history
  • IORails calls that supply generation options now return GenerationResponse, and message lists must be passed with messages= rather than positionally v0.24.0 · Aug 2026 · source · release history
  • IORails calls that supply generation options now return GenerationResponse; message lists must be passed with messages= as a keyword argument rather than positionally. v0.24.0 · Aug 2026 · source · release history
Colang 2.0 scripting language support shipped Provides a preview implementation of the Colang 2.0 syntax and semantics for defining rail logic, including new operators and execution models. 4 releases · first seen Feb 2024

Also counts toward: Scripting language support

release

  • Enables Rails Exception Handling in Colang 1.0 and 2.x v0.10.0 · Sep 2024 · source · release history
  • _generation operator (...) for constructing output sequences within Colang 2.0 flows v0.9.0 · May 2024 · source · release history
  • Colang 1.0 syntax and semantics are no longer the default; Colang 2.0 (Beta) is now included, requiring migration for existing configurations. v0.9.0 · May 2024 · source · release history
  • Adds a preview implementation of Colang 2.0 for early testing. v0.8.0 · Feb 2024 · source · release history
Action return type standardization shipped Requires custom actions to return an explicit RailOutcome instead of using the deprecated output_mapping argument. 3 releases · first seen Aug 2026

release

  • Custom actions using @action(output_mapping=...) must remove that argument and return an explicit RailOutcome from the action v0.24.0 · Aug 2026 · source · release history
  • Custom actions using @action(output_mapping=...) must remove that argument and return an explicit RailOutcome instead. v0.24.0 · Aug 2026 · source · release history
  • Adds RailOutcome — an engine-neutral allow, block, or transform result that both LLMRails and IORails can enforce from a single rail action return value. v0.24.0 · Aug 2026 · source · release history
Multi-rail self-check support shipped Enables running multiple namespaced self-check rails simultaneously with per-rail task prompts. 3 releases · first seen Aug 2026

release

  • Adds multiple namespaced self-check rails with per-rail namespaced task prompts, enabling more than one self-check rail to run in the same configuration. v0.24.0 · Aug 2026 · source · release history
  • Supports running multiple self-check rails simultaneously with per-rail namespaced task prompts. v0.24.0 · Aug 2026 · source · release history
  • Run multiple self-check rails with per-rail namespaced task prompts v0.24.0 · Aug 2026 · source · release history
Rail manifest discovery shipped Declares configuration, actions, execution surfaces, requirements, and privacy properties for built-in rails to enable automatic discovery by engines. 2 releases · 1 other source · first seen Aug 2026

release

  • Adds typed rail manifests so built-in rails declare their configuration, actions, execution surfaces, requirements, and privacy properties for automatic discovery by both engines. v0.24.0 · Aug 2026 · source · release history
  • Adds typed rail manifests so built-in rails can declare their configuration, actions, execution surfaces, requirements, and privacy properties for automatic discovery by both engines. v0.24.0 · Aug 2026 · source · release history

example

  • Run an evaluation task nemoguardrails evaluate
Privacy-focused PII detection integrations shipped Integrates additional specialized PII and privacy protection services, including Private AI, for secure handling of sensitive data. 3 releases · first seen Nov 2024

Also counts toward: ML-based detection

release

  • Adding GLiNER for PII detection (open alternative to PrivateAI) v0.20.0 · Jan 2026 · source · release history
  • Add pii masking capability to PrivateAI integration v0.12.0 · Feb 2025 · source · release history
  • Adds Private AI Integration for private AI use cases v0.11.0 · Nov 2024 · source · release history
Reasoning trace guardrail support shipped Allows applying guardrails to the model's internal reasoning traces before generating the final output, with configuration options for preservation and extraction. 3 releases · first seen Jun 2025

release

  • Reasoning traces are extracted to a separate reasoning field instead of being prepended; use LangChain's additional_kwargs structure. v0.18.0 · Nov 2025 · source · release history
  • Introduces BotThinking events to apply guardrails on an LLM's reasoning traces v0.18.0 · Nov 2025 · source · release history
  • Adds support for preserving and applying guardrails to reasoning traces, controlled by the config key preserve_reasoning_traces (boolean) in Rail YAML definitions. v0.14.0 · Jun 2025 · source · release history
CLI version reporting shipped Displays the installed version of the cyber tooling via the command line interface. 1 release · 2 other sources · first seen Dec 2023

Also counts toward: Command-line interface

release

example

  • Check the installed version of NeMo Guardrails from the terminal. nemo guardrails --version v0.6.1 · Dec 2023 · source
  • Show CLI help and available commands nemoguardrails --help
Content transforming rail support shipped Applies transforming rail outcomes to input and output content in IORails. 2 releases · first seen Aug 2026

release

  • Apply transforming rail outcomes to input and output content in IORails v0.24.0 · Aug 2026 · source · release history
  • Execute blocking rail outcomes directly in IORails via the new RailOutcome allow/block/transform contract v0.24.0 · Aug 2026 · source · release history
Unified telemetry instrumentation shipped Adds shared model telemetry with an instrumented decorator for LLM call observability. 2 releases · first seen Aug 2026

release

  • Add shared model telemetry with an instrumented model decorator v0.24.0 · Aug 2026 · source · release history
  • Adds shared model telemetry and an instrumented model decorator for LLM call observability. v0.24.0 · Aug 2026 · source · release history
File exclusion via .railsignore shipped Adds support for a .railsignore file to exclude specific files from RailsConfig rules processing. 1 release · first seen Nov 2024

release

  • Adds .railsignore file support to exclude specific files from RailsConfig rules v0.11.0 · Nov 2024 · source · release history
Sandboxed Jinja2 template execution shipped Adds a sandboxed environment for Jinja2 templates to enhance security during content generation. 1 release · first seen Nov 2024

release

Configuration migration tools shipped Provides a MigrationTool to convert Colang 1.0 or 2-alpha configurations to the current Colang 2.x standard. 1 release · first seen Sep 2024

release

  • Introduces a MigrationTool for converting Colang 1.0 or 2-alpha configs to Colang 2.x v0.10.0 · Sep 2024 · source · release history
Rails configuration serialization shipped Enables serialization support for the LLMRails class to persist and restore rail configurations. 1 release · first seen Sep 2024

release

  • Implements serialization support for the LLMRails class via llmrails v0.10.0 · Sep 2024 · source · release history
Custom embedding model registration shipped Allows users to register and use custom embedding models via library APIs instead of relying solely on built-in providers. 1 release · first seen Jul 2024

release

  • Enables registering and using custom embedding models via new library APIs v0.9.1 · Jul 2024 · source · release history
Single-call execution mode shipped Combines guardrail checks and response generation into a single LLM call to reduce latency. 1 release · first seen Dec 2023

release

  • Adds rails.dialog.single_call.enabled config to reduce latency by combining guardrails and response generation in a single LLM call v0.6.0 · Dec 2023 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for NeMo Guardrails, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail NeMo Guardrails puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

25 entries

  1. August 20261
  2. July 20261
  3. May 20261
  4. March 20261
  5. January 20261
  6. December 20251
  7. November 20251
  8. October 20251
  9. September 20251
  10. August 20251
  11. July 20251
  12. June 20251
  13. March 20251
  14. February 20251
  15. January 20251
  16. November 20241
  17. September 20241
  18. July 20241
  19. May 20241
  20. April 20241
  21. March 20241
  22. February 20241
  23. January 20241
  24. December 20232
    Show

    25 entries

    Project health

    Issue, contributor and maintainer activity in NVIDIA-NeMo/Guardrails, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 41 −7 vs prior 12 months
    2. Maintainers 2 +2 joined · −4 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 77% of issues opened, last 12 months
    5. Median time to close 289 days first maintainer reply 5.8 days
    6. Open backlog 146 of 619 issues ever filed
    1. Issues opened / month 6 · 4 communitymaintainers
    2. Open backlog 146
    3. Contributors / month 6
    4. Commits / month 9
    5. Stars 7,137
    Issue themes, last 12 months
    • bugs 28%
    • features 28%
    • docs 7%
    • other 37%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →