pirola/context-1-mxfp4-gguf warn
Weights only ship in a format that can run code when loaded; the chat template was dropped from its base model, which changes behavior.
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 (calibration_context1.pt). 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.
medium Chat template dropped vs parent
chromadb/context-1 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.
- Run `ingot patch <owner/model>` — the patch manifest carries the parent's template and applies it to a local copy's `tokenizer_config.json`.
- 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.
- 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.
info Pickle static analysis clean
Opcode-level parse of calibration_context1.pt (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.
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 pirola/context-1-mxfp4-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 | apache-2.0 |
| serialization | gguf pickle |
| chat template | none |
| claimed lineage | chromadb/context-1 |
| lineage verified | unverified — weights battery pending |
Full measured fingerprint
| library | gguf |
| pipeline | text-generation |
| repo files | 5 — pickle: calibration_context1.pt |
| revision | 6a3cfb917702 |
| HF snapshot | 19 downloads · 0 likes · updated 2026-06-07 · captured 2026-08-25 |
| pickle audit | calibration_context1.pt — 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 22:16 | 7s | 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/pirola/context-1-mxfp4-gguf)