Model page

Jurema-br/Jurema-7B warn

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 downloadfailed403 Forbidden for https://huggingface.co/Jurema-br/Jurema-7B/resolve/main/model.safetensors.index.json (gated repo — the HF_TOKEN account has not accepted this repo's license, or the token lacks gated-repo read scope)
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.

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 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 Jurema-br/Jurema-7B

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.

architectureqwen2
parameters7615.6M
licenseapache-2.0
serializationsafetensors
chat templatenone
claimed lineageQwen/Qwen2.5-7B-Instruct
lineage verifiedunverified — weights battery pending
Full measured fingerprint
architecturesQwen2ForCausalLM
repo files16
gatedauto
revision90aa82d3ed8c
HF snapshot5.4k downloads · 67 likes · updated 2025-07-28 · 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/Jurema-br/Jurema-7B/badge.svg)](https://ingot.tools/models/Jurema-br/Jurema-7B)
Gate it in CI