Model page

nvidia/Eagle2.5-8B warn

Loading it runs custom code from the repo; its license differs from its base model's; the chat template was dropped from its base model, which changes behavior.

downloads 59.6klikes 48license otherarch eagle_2_5_vlparams 8070.8Mupdated 2025-11-29

claims base: Qwen/Qwen2.5-7B-Instruct, google/siglip2-so400m-patch16-512 · chat template: present · view on Hugging Face ↗

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/Eagle2.5-8B
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 Repo ships executable Python (trust_remote_code)

The repository contains custom code files that run in-process when loaded with trust_remote_code=True. Pin the revision hash and review the code before loading.

How to fix

Review and pin the custom code; never float on `main` with trust_remote_code=True.

  1. Read every `.py` file in the repo before first load — this code runs in your process.
  2. Pin the revision: `from_pretrained(model_id, revision="<commit sha>", trust_remote_code=True)` so a later push can't swap the code under you.
  3. Prefer a version of the architecture already in `transformers` if one exists, which removes the remote-code requirement entirely.

info Gated repository

Access requires accepting the owner's terms; check the gate conditions for redistribution and field-of-use limits.

How to fix

Read the gate terms before building on the model.

  1. Check the gate conditions on the Hugging Face repo for redistribution and field-of-use limits — they bind your deployment, not just your download.

info Gated repo files unreadable — file-level checks skipped

config.json and tokenizer_config.json could not be read, so chat-template, architecture, and vocab checks did not run. Full scans of gated repos need the service's HF_TOKEN account to have accepted this repo's license on Hugging Face.

How to fix

Read the gate terms before building on the model.

  1. Check the gate conditions on the Hugging Face repo for redistribution and field-of-use limits — they bind your deployment, not just your download.

medium License differs from claimed parent (other vs apache-2.0)

This model declares other while its claimed base Qwen/Qwen2.5-7B-Instruct declares apache-2.0. 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

Qwen/Qwen2.5-7B-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/Eagle2.5-8B

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.

architectureeagle_2_5_vl
parameters8070.8M
licenseother
serializationsafetensors custom code
chat templatenone
claimed lineageQwen/Qwen2.5-7B-Instruct, google/siglip2-so400m-patch16-512
lineage verifiedunverified — weights battery pending
Full measured fingerprint
architecturesEagle2_5_VLForConditionalGeneration
librarytransformers
pipelineimage-text-to-text
repo files23
gatedauto
revision61e45235a1e4
HF snapshot82.0k downloads · 47 likes · updated 2025-11-29 · 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/Eagle2.5-8B/badge.svg)](https://ingot.tools/models/nvidia/Eagle2.5-8B)
Gate it in CI