Model page

lapisrocks/Llama-3-8B-Instruct-TAR-Bio-v2 warn

downloads 533likes 0license apache-2.0arch llamaparams 8030.3Mupdated 2024-10-14

claims base: meta-llama/Meta-Llama-3-8B-Instruct · chat template: not found · view on Hugging Face ↗

Scan coverage

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

BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-21
Weights batteryWeights forensics — no GPU, no downloadcomplete 2026-08-21128,256-token embedding scanned · 715 undertrained
Behavioral batteryLive-inference differentialsnot run

Findings

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

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

This model declares apache-2.0 while its claimed base meta-llama/Meta-Llama-3-8B-Instruct declares llama3. 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.

low Undertrained tokens in vocabulary (non-ASCII tail)

Embedding-norm scan flagged 715 undertrained tokens (norm < 0.3× the vocabulary median), but 0 decode to plain-ASCII strings, so exposure in English-language pipelines is limited. Behavioral confirmation requires the behavioral battery.

How to fixruntime guardweight-level

Keep the affected token strings out of the model's input — the scan-derived runtime guard carries this model's exact blocklist.

  1. Fetch this model's guard artifact (`/api/v1/guard/<owner>/<model>`): the confirmed corrupting tokens and the low-norm candidate list, derived from the published scan.
  2. Screen inbound text with it (the `@ingotai/guard` package is a reference implementation) and route flagged records to a different model or human review — verbatim-copy tasks on flagged strings are the failure mode.
  3. The underlying cause is undertrained embeddings in the weights; a true fix is weight-level (continued pretraining on the affected tokens) — that is not a patch, it's a training job.

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
parameters8030.3M
vocabulary128,256 tokens
licenseapache-2.0
serializationsafetensors
chat templatenone
claimed lineagemeta-llama/Meta-Llama-3-8B-Instruct
lineage verifiedunverified — weights battery pending
glitch-token surface715 undertrained candidates, 0 plain-ASCII
Full measured fingerprint
architecturesLlamaForCausalLM
repo files12
revision143c907d0ffa
HF snapshot538 downloads · 0 likes · updated 2024-10-14 · captured 2026-08-21
embedding tensormodel.embed_tokens.weight · F32 · 128,256×4096
embedding normsmedian 0.6015 · mean 0.5915
lineage checkparent weights unreadable (403 Forbidden for https://huggingface.co/meta-llama/Meta-Llama-3-8B-Instruct/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))

Battery runs

The run trace behind the findings above: every deep-battery job for this model, with what each run measured or why it failed. Findings are only as good as the runs that produced them.

batterystatusqueueddurationattempts
weightscomplete2026-08-21 05:142m1
weights run 2026-08-21 measurements
probes runglitch-norm-scan, lineage-norm-correlation
probes skippedtoken-decode: no tokenizer.json
embedding tensormodel.embed_tokens.weight · F32 · 128,256×4096
glitch surface715 undertrained, 0 plain-ASCII
lineage checknot checked (parent weights unreadable (403 Forbidden for https://huggingface.co/meta-llama/Meta-Llama-3-8B-Instruct/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)))

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/lapisrocks/Llama-3-8B-Instruct-TAR-Bio-v2/badge.svg)](https://ingot.tools/models/lapisrocks/Llama-3-8B-Instruct-TAR-Bio-v2)
Gate it in CI