Model page

nvidia/GLM-5.2-NVFP4 warn

downloads 1.2Mlikes 315license mitarch glm_moe_dsaparams 380989.1Mupdated 2026-06-26

claims base: zai-org/GLM-5.2 · chat template: present · view on Hugging Face ↗

Scan coverage

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

BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-22
Weights batteryWeights forensics — no GPU, no downloadcomplete 2026-08-22154,880-token embedding scanned · 1357 undertrained · lineage consistent
Behavioral batteryLive-inference differentialsnot run

Findings

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

medium Undertrained (glitch) token surface in vocabulary

Embedding-norm scan flagged 1357 undertrained tokens (norm < 0.3× the vocabulary median of 0.723), including 185 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "_ComCallableWrapper", "ForCanBeConvertedToF", "estattet", "$PostalCodesNL", "ForCanBeConverted", "irsiniz", "unehmen", "ociazione". 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 zai-org/GLM-5.2

Mean cosine similarity of 64 sampled token-embedding rows against zai-org/GLM-5.2 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.

  1. If you own the repo: correct the `base_model` field in the model card metadata to the real, public parent.
  2. If you don't: identify the true parent (config architecture + weight shapes narrow it fast) and re-scan with that lineage in mind.

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-22.

architectureglm_moe_dsa · 78 layers · 6144-dim
parameters380989.1M
vocabulary154,880 tokens
licensemit
serializationsafetensors
chat templatenone
claimed lineagezai-org/GLM-5.2
lineage verifiedconsistent vs zai-org/GLM-5.2 — embedding-row cosine 1.000
glitch-token surface1,357 undertrained candidates, 185 plain-ASCII
Full measured fingerprint
architecturesGlmMoeDsaForCausalLM
libraryModel Optimizer
pipelinetext-generation
repo files57
revisionaec724e8c7b8
HF snapshot1.2M downloads · 315 likes · updated 2026-06-26 · captured 2026-08-21
embedding tensormodel.embed_tokens.weight · BF16 · 154,880×6144
embedding normsmedian 0.723 · mean 0.7022
lineage checkconsistent — cosine 1 over 64 sampled rows vs zai-org/GLM-5.2
glitch-token samples"_ComCallableWrapper", "ForCanBeConvertedToF", "estattet", "$PostalCodesNL", "ForCanBeConverted", "irsiniz", "unehmen", "ociazione", "_typeDefinitionSize", "PostalCodesNL", "zainteres", "abilirsiniz"

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 07:432m1
weights run 2026-08-21 measurements
probes runglitch-norm-scan, lineage-norm-correlation
embedding tensormodel.embed_tokens.weight · BF16 · 154,880×6144
glitch surface1,357 undertrained, 185 plain-ASCII
lineage checkconsistent — cosine 1 over 64 rows vs zai-org/GLM-5.2

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/GLM-5.2-NVFP4/badge.svg)](https://ingot.tools/models/nvidia/GLM-5.2-NVFP4)
Gate it in CI