Model page

bytedance-research/ChatTS-8B warn

Weights only ship in a format that can run code when loaded; loading it runs custom code from the repo; the chat template was dropped from its base model, which changes behavior. Plus 1 more issue.

downloads 1.1klikes 10license apache-2.0arch qwen3tsupdated 2025-12-29

claims base: Qwen/Qwen3-8B · chat template: present · view on Hugging Face ↗

Scan coverageStatic battery2026-08-21Weights battery2026-08-21Behavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-21
Weights batteryWeights forensics: no GPU, no downloadcomplete 2026-08-21151,936-token embedding scanned · 2999 undertrained · lineage consistent · pickle audit clean
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.

medium Pickle-serialized weights, no safetensors

Weights ship only as pickle-based files (pytorch_model-00001-of-00004.bin, pytorch_model-00002-of-00004.bin, pytorch_model-00003-of-00004.bin, …). Loading pickle executes arbitrary code from the file — prefer a safetensors release or load in a sandbox.

How to fix

Convert the weights to safetensors before loading them anywhere that matters.

  1. Do not load the pickle files in-process — pickle deserialization executes arbitrary code from the file.
  2. Convert locally in a sandbox: `pip install safetensors` and use `safetensors.torch.save_file` on a state dict loaded with `torch.load(..., weights_only=True)` (refuses most code-execution payloads), or use Hugging Face's `convert.py` space/script.
  3. Pin the exact revision hash you converted from, and load only your converted safetensors artifact from then on.

medium Repo ships executable Python (trust_remote_code)

The repository contains custom code files that run in-process when loaded with trust_remote_code=True. Pin the revision hash and review the code before loading.

How to fix

Review and pin the custom code; never float on `main` with trust_remote_code=True.

  1. Read every `.py` file in the repo before first load — this code runs in your process.
  2. Pin the revision: `from_pretrained(model_id, revision="<commit sha>", trust_remote_code=True)` so a later push can't swap the code under you.
  3. Prefer a version of the architecture already in `transformers` if one exists, which removes the remote-code requirement entirely.

medium Chat template dropped vs parent

Qwen/Qwen3-8B 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.

medium Undertrained (glitch) token surface in vocabulary

Embedding-norm scan flagged 2999 undertrained tokens (norm < 0.3× the vocabulary median of 1.451), including 102 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "$PostalCodesNL", "ForCanBeConvertedToF", "PostalCodesNL", "ForCanBeConverted", "useRalative", "thuisontvangst", "useRal", "sexkontakte". 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 Pickle static analysis clean

Opcode-level parse of pytorch_model-00001-of-00004.bin, pytorch_model-00002-of-00004.bin, pytorch_model-00003-of-00004.bin, pytorch_model-00004-of-00004.bin (no code executed) found only standard serialization globals (3 distinct, all torch/collections/numpy). Pickle remains an executable format — this verifies the current bytes, not future uploads; prefer a safetensors release.

info Weights consistent with claimed parent Qwen/Qwen3-8B

Mean cosine similarity of 64 sampled token-embedding rows against Qwen/Qwen3-8B is 1.000 — the weights plausibly descend from the declared base (relation: unspecified).

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 bytedance-research/ChatTS-8B

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.

architectureqwen3ts · 36 layers · 4096-dim
vocabulary151,936 tokens
licenseapache-2.0
serializationno safetensors pickle custom code
chat templatenone
claimed lineageQwen/Qwen3-8B
lineage verifiedconsistent vs Qwen/Qwen3-8B — embedding-row cosine 1.000
glitch-token surface2,999 undertrained candidates, 102 plain-ASCII
Full measured fingerprint
architecturesQwen3TSForCausalLM
librarytransformers
pipelinetext-generation
repo files21 — pickle: pytorch_model-00001-of-00004.bin, pytorch_model-00002-of-00004.bin, pytorch_model-00003-of-00004.bin, pytorch_model-00004-of-00004.bin
revision7216a8403406
HF snapshot1.5k downloads · 10 likes · updated 2025-12-29 · captured 2026-08-21
pickle auditpytorch_model-00001-of-00004.bin, pytorch_model-00002-of-00004.bin, pytorch_model-00003-of-00004.bin, pytorch_model-00004-of-00004.bin — 3 standard global(s)
embedding tensormodel.embed_tokens.weight · F16 · 151,936×4096
embedding normsmedian 1.4512 · mean 1.3758
lineage checkconsistent — cosine 1 over 64 sampled rows vs Qwen/Qwen3-8B
glitch-token samples"$PostalCodesNL", "ForCanBeConvertedToF", "PostalCodesNL", "ForCanBeConverted", "useRalative", "thuisontvangst", "useRal", "sexkontakte", "NdrFc", "webElementX", "sextreffen", "wannonce"
Battery runs (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightscomplete2026-08-21 05:125m2
weights run 2026-08-21 — measurements
probes runglitch-norm-scan, pickle-static-analysis, lineage-norm-correlation
embedding tensormodel.embed_tokens.weight · F16 · 151,936×4096
glitch surface2,999 undertrained, 102 plain-ASCII
lineage checkconsistent — cosine 1 over 64 rows vs Qwen/Qwen3-8B

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/bytedance-research/ChatTS-8B/badge.svg)](https://ingot.tools/models/bytedance-research/ChatTS-8B)
Gate it in CI