Model page

nvidia/Llama-3.1-8B-Instruct-NVFP4 warn

Its license differs from its base model's; the chat template was dropped from its base model, which changes behavior.

Could not load this model from the Hugging Face API (private, gated, or nonexistent). Findings below are from our archive.

Scan coverageStatic battery2026-08-21Weights batteryfailedBehavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-21
Weights batteryWeights forensics — no GPU, no downloadfailed429 Too Many Requests for https://huggingface.co/api/models/nvidia/Llama-3.1-8B-Instruct-NVFP4
Behavioral batteryLive-inference differentialsnot run

Ingot runs three batteries against a model. What each one checks →

Findings

Scanned 2026-08-21 · published from a community scan.

medium License differs from claimed parent (other vs llama3.1)

This model declares other while its claimed base meta-llama/Llama-3.1-8B-Instruct declares llama3.1. Verify the re-license is permitted before commercial use.

How to fix

Verify the re-license is actually permitted before relying on it.

  1. Read the parent's license for derivative-work and re-licensing terms — many open-weight licenses (e.g. Llama-family) do not permit arbitrary re-licensing.
  2. If the re-license is not permitted, the parent's terms govern your use regardless of what this repo declares.

medium Chat template dropped vs parent

meta-llama/Llama-3.1-8B-Instruct ships a chat template; this repo does not. Serving stacks will silently fall back to a generic template, changing behavior. (In our 296-model census, 78% of pure quantization re-releases changed or dropped the template.)

How to fixingot patch

Restore the parent's chat template in `tokenizer_config.json` — a pure metadata fix.

  1. Run `ingot patch <owner/model>` — the patch manifest carries the parent's template and applies it to a local copy's `tokenizer_config.json`.
  2. Or fix by hand: copy the `chat_template` value from the parent repo's `tokenizer_config.json` into this model's, and pin your serving stack to that file.
  3. If the drift was intentional (the author retrained on a new template), confirm that in the model card before "fixing" it — restoring the parent template on retrained weights changes behavior too.

Fix it

Some findings are metadata-level and patchable — apply the fixes to your local copy (your weights never leave your machine):

npx @ingotai/scan patch nvidia/Llama-3.1-8B-Instruct-NVFP4

Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the model.

Fingerprint

The durable profile of this model: measured weights-and-metadata facts, rebuilt on every scan and battery run. Updated 2026-08-21.

architecturellama · 32 layers · 4096-dim
parameters4540.6M
vocabulary128,256 tokens
licenseother
serializationsafetensors
chat templatenone
claimed lineagemeta-llama/Llama-3.1-8B-Instruct
lineage verifiedunverified — weights battery pending
Full measured fingerprint
architecturesLlamaForCausalLM
libraryModel Optimizer
repo files13
revisionbdb54e242984
HF snapshot136.0k downloads · 15 likes · updated 2025-09-15 · captured 2026-08-21

Verdict badge

Ship the verdict in your README — it always shows the latest published analysis:

Ingot verdict: warn

[![Ingot scan](https://ingot.tools/api/v1/models/nvidia/Llama-3.1-8B-Instruct-NVFP4/badge.svg)](https://ingot.tools/models/nvidia/Llama-3.1-8B-Instruct-NVFP4)
Gate it in CI