Model page

hypaai/Hypa-Llama3.1-8b-SFT 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. Plus 1 minor note.

downloads 1.6klikes 0license apache-2.0arch llamaparams 8030.3Mupdated 2026-05-21

claims base: meta-llama/Llama-3.1-8B-Instruct · chat template: present · view on Hugging Face ↗

Scan coverageStatic battery2026-08-27Weights battery2026-08-21Behavioral batterycompletedetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-27
Weights batteryWeights forensics: no GPU, no downloadcomplete 2026-08-21128,256-token embedding scanned · 497 undertrained · lineage consistent
Behavioral batteryLive-inference differentialscompletefull differential battery (curated)

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

Findings

Scanned 2026-08-27 · 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/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 differs from claimed parent

The chat template does not match meta-llama/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.

  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.

medium Undertrained (glitch) token surface in vocabulary

Embedding-norm scan flagged 497 undertrained tokens (norm < 0.3× the vocabulary median of 0.688), including 141 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "$PostalCodesNL", "ForCanBeConverted", "TokenNameIdentifier", "useRalative", "ForCanBeConvertedToF", "PostalCodesNL", "ilmektedir", "CLIIIK". 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.

  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.

info Weights consistent with claimed parent meta-llama/Llama-3.1-8B-Instruct

Mean cosine similarity of 64 sampled token-embedding rows against meta-llama/Llama-3.1-8B-Instruct is 0.999 — the weights plausibly descend from the declared base (relation: unspecified).

low Partial glitch-token echo degradation

Echo failures on 14/16 undertrained tokens vs 2/8 controls — a differential exists but below the confirmation bar (≥50% glitch failures with clean controls).

Put this result in your workflow

Check every checkpoint before it ships

Use the web app, API, CLI, or CI gate to scan candidate checkpoints and catch model drift before deployment. Public-model scans publish to the open database; paid plans add the volume needed for continuous checks.

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 hypaai/Hypa-Llama3.1-8b-SFT

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 templatepresent · sha256:13fa181e503beab6
claimed lineagemeta-llama/Llama-3.1-8B-Instruct
lineage verifiedconsistent vs meta-llama/Llama-3.1-8B-Instruct — embedding-row cosine 0.999
glitch-token surface497 undertrained candidates, 141 plain-ASCII
Full measured fingerprint
architecturesLlamaForCausalLM
librarytransformers
pipelinetext-generation
repo files13
revision030c33bcd2f1
HF snapshot1.0k downloads · 0 likes · updated 2026-05-21 · captured 2026-08-21
embedding tensormodel.embed_tokens.weight · BF16 · 128,256×4096
embedding normsmedian 0.6878 · mean 0.6741
lineage checkconsistent — cosine 0.9993 over 64 sampled rows vs meta-llama/Llama-3.1-8B-Instruct
glitch-token samples"$PostalCodesNL", "ForCanBeConverted", "TokenNameIdentifier", "useRalative", "ForCanBeConvertedToF", "PostalCodesNL", "ilmektedir", "CLIIIK", "_ComCallableWrapper", "krvldkf", "webElementXpaths", "sahuje"
Battery runs (2)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
gpucomplete2026-08-27 04:312m1
weightscomplete2026-08-21 05:122m1
gpu run 2026-08-27 — measurements
probes runglitch
weights run 2026-08-21 — measurements
probes runglitch-norm-scan, lineage-norm-correlation
embedding tensormodel.embed_tokens.weight · BF16 · 128,256×4096
glitch surface497 undertrained, 141 plain-ASCII
lineage checkconsistent — cosine 0.9993 over 64 rows vs meta-llama/Llama-3.1-8B-Instruct

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/hypaai/Hypa-Llama3.1-8b-SFT/badge.svg)](https://ingot.tools/models/hypaai/Hypa-Llama3.1-8b-SFT)
Gate it in CI