Vikhrmodels/Vikhr-Llama3.1-8B-Instruct-R-21-09-24 warn
Its license differs from its base model's; the chat template differs from its base model, which changes behavior; glitch tokens that can silently corrupt ordinary input.
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 battery2026-08-21Behavioral batterynot rundetails
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-21 |
| Weights battery | Weights forensics — no GPU, no download | complete 2026-08-21128,256-token embedding scanned · 497 undertrained · lineage consistent |
| Behavioral battery | Live-inference differentials | not 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 (apache-2.0 vs llama3.1)
This model declares apache-2.0 while its claimed base meta-llama/Meta-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.
- 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.
- If the re-license is not permitted, the parent's terms govern your use regardless of what this repo declares.
medium Chat template differs from claimed parent
The chat template does not match meta-llama/Meta-Llama-3.1-8B-Instruct's. Template drift silently changes model behavior even when weights are identical — 37% of drifted derivatives in our census left it undisclosed. Diff the templates before deploying.
How to fixingot patch
Restore the parent's chat template in `tokenizer_config.json` — a pure metadata fix.
- Run `ingot patch <owner/model>` — the patch manifest carries the parent's template and applies it to a local copy's `tokenizer_config.json`.
- 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.
- 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.
medium Undertrained (glitch) token surface in vocabulary
Embedding-norm scan flagged 497 undertrained tokens (norm < 0.3× the vocabulary median of 0.685), including 140 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "ilmektedir", "$PostalCodesNL", "ForCanBeConvertedToF", "TokenNameIdentifier", "CLIIIK", "useRalative", "PostalCodesNL", "_ComCallableWrapper". In models where this class was tested behaviorally, such tokens silently rewrote user input into confident, schema-valid, wrong output. These are candidates from the weights alone; 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.
- 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.
- 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.
- 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.
info Weights consistent with claimed parent meta-llama/Meta-Llama-3.1-8B-Instruct
Mean cosine similarity of 64 sampled token-embedding rows against meta-llama/Meta-Llama-3.1-8B-Instruct is 1.000 — the weights plausibly descend from the declared base (relation: unspecified).
How to fix
Fix or verify the `base_model` declaration so lineage checks can run.
- If you own the repo: correct the `base_model` field in the model card metadata to the real, public parent.
- If you don't: identify the true parent (config architecture + weight shapes narrow it fast) and re-scan with that lineage in mind.
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 Vikhrmodels/Vikhr-Llama3.1-8B-Instruct-R-21-09-24
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.
| architecture | llama · 32 layers · 4096-dim |
| parameters | 8030.3M |
| vocabulary | 128,256 tokens |
| license | apache-2.0 |
| serialization | safetensors |
| chat template | present · sha256:9417d7e83e1fc534 |
| claimed lineage | meta-llama/Meta-Llama-3.1-8B-Instruct, meta-llama/Llama-3.1-8B-Instruct |
| lineage verified | consistent vs meta-llama/Meta-Llama-3.1-8B-Instruct — embedding-row cosine 1.000 |
| glitch-token surface | 497 undertrained candidates, 140 plain-ASCII |
Full measured fingerprint
| architectures | LlamaForCausalLM |
| repo files | 15 |
| revision | 3d76e0f58bd5 |
| HF snapshot | 55.5k downloads · 34 likes · updated 2024-09-26 · captured 2026-08-21 |
| embedding tensor | model.embed_tokens.weight · BF16 · 128,256×4096 |
| embedding norms | median 0.6849 · mean 0.6713 |
| lineage check | consistent — cosine 1 over 64 sampled rows vs meta-llama/Meta-Llama-3.1-8B-Instruct |
| glitch-token samples | "ilmektedir", "$PostalCodesNL", "ForCanBeConvertedToF", "TokenNameIdentifier", "CLIIIK", "useRalative", "PostalCodesNL", "_ComCallableWrapper", "ForCanBeConverted", "krvldkf", "sahuje", "webElementXpaths" |
Battery runs (1)the run trace behind the findings — what each job measured
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| weights | complete | 2026-08-21 05:09 | 47s | 1 |
weights run 2026-08-21 — measurements
| probes run | glitch-norm-scan, lineage-norm-correlation |
| embedding tensor | model.embed_tokens.weight · BF16 · 128,256×4096 |
| glitch surface | 497 undertrained, 140 plain-ASCII |
| lineage check | consistent — cosine 1 over 64 rows vs meta-llama/Meta-Llama-3.1-8B-Instruct |
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/Vikhrmodels/Vikhr-Llama3.1-8B-Instruct-R-21-09-24)