reaperdoesntknow/MoA-150M warn
Weights only ship in a format that can run code when loaded; Chat template ends turns with <|im_end|>, which is not a configured stop token. Plus 1 minor note.
chat template: present · view on Hugging Face ↗
Scan coverageStatic battery2026-08-25Weights battery2026-08-25Behavioral batterynot rundetails
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-25 |
| Weights battery | Weights forensics — no GPU, no download | complete 2026-08-25no token vocabulary — pickle audit only · pickle audit clean |
| Behavioral battery | Live-inference differentials | not run |
Ingot runs three batteries against a model. What each one checks →
Findings
Scanned 2026-08-25 · published from a community scan.
medium Pickle-serialized weights, no safetensors
Weights ship only as pickle-based files (pytorch_model.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.
- Do not load the pickle files in-process — pickle deserialization executes arbitrary code from the file.
- 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.
- Pin the exact revision hash you converted from, and load only your converted safetensors artifact from then on.
low Padding token is the EOS token
The pad token and the (only) EOS token are the same. Fine-tuning frameworks mask pad positions out of the loss, so training on this checkpoint teaches the model to never emit EOS — the Phi-4 / Qwen 2.5 / DeepSeek R1 infinite-generation bug. Safe to serve, hazardous to fine-tune; repoint pad_token at a dedicated token first.
How to fixingot patch
Align the stop-token declarations — a pure metadata fix to `generation_config.json` (and `config.json`).
- Identify the token the chat template actually ends assistant turns with (e.g. `<|eot_id|>`, `<end_of_turn>`, `<|im_end|>`) and make sure its id is in `generation_config.json`'s `eos_token_id` list.
- Keep `config.json`'s `eos_token_id` consistent with (or a subset of) `generation_config.json`'s — runtimes differ in which file they read.
- For the pad-equals-EOS hazard: repoint `pad_token` at a dedicated padding token before fine-tuning; serving is unaffected.
- Until the repo is fixed, pass explicit stop tokens to your serving stack (e.g. vLLM `stop_token_ids`, llama.cpp `--override-kv tokenizer.ggml.eos_token_id`).
medium Chat template ends turns with <|im_end|>, which is not a configured stop token
The chat template terminates assistant turns with <|im_end|>, but the effective EOS set (config.json ∪ generation_config.json = [151643] → ["<|endoftext|>"]) never stops on it. Config-honoring runtimes generate past the terminator until the token budget is exhausted — runaway cost and self-continuing fake turns. Add <|im_end|>'s id to generation_config.json's eos_token_id.
How to fixingot patch
Align the stop-token declarations — a pure metadata fix to `generation_config.json` (and `config.json`).
- Identify the token the chat template actually ends assistant turns with (e.g. `<|eot_id|>`, `<end_of_turn>`, `<|im_end|>`) and make sure its id is in `generation_config.json`'s `eos_token_id` list.
- Keep `config.json`'s `eos_token_id` consistent with (or a subset of) `generation_config.json`'s — runtimes differ in which file they read.
- For the pad-equals-EOS hazard: repoint `pad_token` at a dedicated padding token before fine-tuning; serving is unaffected.
- Until the repo is fixed, pass explicit stop tokens to your serving stack (e.g. vLLM `stop_token_ids`, llama.cpp `--override-kv tokenizer.ggml.eos_token_id`).
info Pickle static analysis clean
Opcode-level parse of pytorch_model.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.
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 reaperdoesntknow/MoA-150M
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-25.
| architecture | moa_metric · 8 layers |
| vocabulary | 151,665 tokens |
| license | apache-2.0 |
| serialization | no safetensors pickle |
| chat template | present (chat_template.jinja) · sha256:44d5f08f3f72b837 |
Full measured fingerprint
| architectures | MoAMetricLM |
| library | transformers |
| pipeline | text-generation |
| repo files | 16 — pickle: pytorch_model.bin |
| revision | e575a3e51a48 |
| HF snapshot | 2.6k downloads · 2 likes · updated 2026-08-18 · captured 2026-08-25 |
| weights battery | token-embedding scan n/a — no token-embedding tensor found in the pickle checkpoint(s) — pickle checkpoint(s) statically analyzed anyway |
| pickle audit | pytorch_model.bin — 3 standard global(s) |
Battery runs (1)the run trace behind the findings — what each job measured
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| weights | complete | 2026-08-25 21:46 | 3s | 1 |
weights run 2026-08-25 — measurements
| probes run | pickle-static-analysis |
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/reaperdoesntknow/MoA-150M)