Will it last?
This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Common problems & fixes
Typical pitfalls for a small multimodal hybrid Mamba-Transformer MoE are multimodal preprocessing and processor-config mismatches, kernel-to-engine version mismatches for the Mamba-2 and MoE layers, the wrong repo path because of the missing "NVIDIA-" prefix, and revision drift on download. Match engine and kernel versions to the documented stack, confirm the processor config, pin the revision and verify checksums. The list is not exhaustive.
Versions, changelog & cadence
Nemotron 3 Nano Omni was released on 2026-04-20 (BF16; FP8 and NVFP4 followed on 2026-04-24, and
build.nvidia.com on 2026-04-28) on the verified nvidia org. There is no single-checkpoint
changelog; the Hugging Face revision hash is the anchor, so pin it. The licence version line is
"v. March 9, 2026" while its web page shows an April 2, 2026 release date.
Security / vulnerability disclosure
NVIDIA maintains a general corporate product-security reporting path
(nvidia.com/en-us/security/). No model-specific vulnerability-disclosure policy for Nemotron is
confirmed, so route model-level issue reports through the Hugging Face and GitHub org presence.
Community & support channels
Support is the NVIDIA open-model presence: the nvidia Hugging Face org (model discussions), the
NVIDIA-NeMo GitHub organisation (the omni3 recipe and NeMo Guardrails), and the NVIDIA/garak
repository for red-team and safety-tooling questions.
Tracked known issues
The recurring caveats are the weaker open-data posture and unadvertised recipe, the absence of a model-level safety evaluation over the multimodal input path, and the two dates on the licence page. Track them against your own control stack and red-team, as no published issue tracker covers them.
How this scores
The ownership factor this domain covers, drawn from the one entry record.
TransparencyDo you know what it is: weights, training, behaviour, and legible terms?
Moderateopen_weights, not open_weights_recipe. The weights are ungated and inspectable and there is a model card and licence, but the card does not carry the family's open-data/recipe self-description, links only an image-training dataset, and the recipe that exists surfaces only the public subset. The weights are visible but the data and full recipe are not clearly released, which is the anchor for moderate, not strong.
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.