MZAIST/MZAIST-v1-Online-LLM warn
Weights only ship in a format that can run code when loaded; loading it runs custom code from the repo; its license differs from its base model's. Plus 1 more issue.
claims base: meta-llama/Llama-3.1-8B, lelapa/InkubaLM-0.4B, mistralai/Mistral-7B-v0.1 · chat template: not found · view on Hugging Face ↗
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-26no 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-26 · 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.
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.
- Read every `.py` file in the repo before first load — this code runs in your process.
- 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.
- Prefer a version of the architecture already in `transformers` if one exists, which removes the remote-code requirement entirely.
medium License differs from claimed parent (apache-2.0 vs llama3.1)
This model declares apache-2.0 while its claimed base meta-llama/Llama-3.1-8B declares llama3.1. Verify the re-license is permitted before commercial use.
How to fix
Verify the re-license is actually permitted before relying on it.
- Read the parent's license for derivative-work and re-licensing terms — many open-weight licenses (e.g. Llama-family) do not permit arbitrary re-licensing.
- If the re-license is not permitted, the parent's terms govern your use regardless of what this repo declares.
medium Vocabulary size differs from claimed parent (61788 vs 128256)
A changed vocab means changed tokenization: strings will split differently than on meta-llama/Llama-3.1-8B, which can shift behavior on identifiers, codes, and non-English text.
How to fixweight-level
Not patchable: the vocab size mirrors the embedding matrix in the weights. Verify the change was intentional.
- Do not edit `vocab_size` in config.json to "match the parent" — it must equal the embedding table in the shipped weights or the model won't load.
- Diff the tokenizers (`tokenizer.json` / added_tokens) against the parent to see what was added or removed, and test your own identifiers, codes, and non-English text through both.
- If the drift is unexplained by the model card, treat tokenization-sensitive behavior as unvalidated on this model.
info Pickle static analysis clean
Opcode-level parse of pytorch_model.bin (no code executed) found only standard serialization globals (5 distinct, all torch/collections/numpy). Pickle remains an executable format — this verifies the current bytes, not future uploads; prefer a safetensors release.
Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the model.
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.
Fingerprint
The durable profile of this model: measured weights-and-metadata facts, rebuilt on every scan and battery run. Updated 2026-08-26.
| architecture | llama · 8 layers · 2048-dim |
| vocabulary | 61,788 tokens |
| license | apache-2.0 |
| serialization | no safetensors pickle custom code |
| chat template | none |
| claimed lineage | meta-llama/Llama-3.1-8B, lelapa/InkubaLM-0.4B, mistralai/Mistral-7B-v0.1 |
| lineage verified | unverified — weights battery pending |
Full measured fingerprint
| architectures | LlamaForCausalLM |
| library | transformers |
| pipeline | text-generation |
| repo files | 10 — pickle: pytorch_model.bin |
| revision | 5b5e014d3131 |
| HF snapshot | 16 downloads · 0 likes · updated 2025-09-30 · 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 — 5 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:23 | 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/MZAIST/MZAIST-v1-Online-LLM)