s3nh/Metabird-7B-GGUF warn
Weights only ship in a format that can run code when loaded; GGUF template ends turns with <|im_end|> but the file stops on </s>. Plus 1 minor note.
Could not load this model from the Hugging Face API (private, gated, or nonexistent). Findings below are from our archive.
Scan coverageStatic battery2026-08-26Weights battery2026-08-26Behavioral batterynot rundetails
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-26 |
| Weights battery | Weights forensics — no GPU, no download | complete 2026-08-26pickle audit clean |
| Behavioral battery | Live-inference differentials | not run |
Ingot runs three batteries against a model. What each one checks →
Findings
Scanned 2026-08-26 · published from a community scan.
medium Pickle-serialized weights, no safetensors
Weights ship only as pickle-based files (metabird-7b.fp16.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.
info Pickle static analysis clean
Opcode-level parse of metabird-7b.fp16.bin (no code executed) found only standard serialization globals (0 distinct, all torch/collections/numpy). Pickle remains an executable format — this verifies the current bytes, not future uploads; prefer a safetensors release.
low Pickle checkpoint only partially analyzable
Static analysis could not fully parse: metabird-7b.fp16.bin: legacy parse stopped after 0 pickle(s): unsupported pickle opcode 0x1 at 9. Unparsed content is unverified.
medium GGUF template ends turns with <|im_end|> but the file stops on </s>
The embedded chat template terminates assistant turns with <|im_end|>, while tokenizer.ggml.eos_token_id points at </s> (2). llama.cpp-family runtimes stop on the metadata EOS, so generation runs past the terminator until the token budget is exhausted. Fix the eos_token_id in the GGUF metadata (gguf-py, no requant needed).
How to fixingot patch
Fix the GGUF's embedded metadata in place with gguf-py — template, EOS id, and pre-tokenizer are all metadata-editable; no requant needed.
- Template or EOS drift: copy the current values from the source repo and write them into the GGUF (`gguf_set_metadata.py` / gguf-py) — the tensor data is untouched.
- Missing pre-tokenizer type: reconvert with a current `convert_hf_to_gguf.py`, or set the correct `tokenizer.ggml.pre` for the architecture.
- Until the file is fixed, override at load time: llama.cpp `--override-kv tokenizer.ggml.eos_token_id=int:<id>` and `--chat-template-file <fixed.jinja>`.
- Prefer a re-upload from the quantizer once the source repo's fix lands — already-downloaded GGUFs never pick up upstream fixes on their own.
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 s3nh/Metabird-7B-GGUF
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-26.
| license | openrail |
| serialization | gguf pickle |
| chat template | none |
Full measured fingerprint
| library | transformers |
| pipeline | text-generation |
| repo files | 8 — pickle: metabird-7b.fp16.bin |
| revision | dcfcc83d6e8e |
| HF snapshot | 64 downloads · 0 likes · updated 2024-01-20 · captured 2026-08-25 |
| pickle audit | metabird-7b.fp16.bin — 0 standard global(s) · legacy (pre-1.6) format, head-scan only |
Battery runs (1)the run trace behind the findings — what each job measured
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| weights | complete | 2026-08-25 21:57 | 4s | 1 |
weights run 2026-08-25 — measurements
| probes run | gguf-metadata |
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/s3nh/Metabird-7B-GGUF)