Model page

MBZUAI-LLM/LLaMA-7B-GLoRA-ShareGPT warn

Weights only ship in a format that can run code when loaded; loading it runs custom code from the repo; no license declared — no usage rights by default. Plus 1 more issue.

downloads 19likes 4license none declaredarch llamaupdated 2023-11-18

chat template: not found · view on Hugging Face ↗

Scan coverageStatic battery2026-08-27Weights battery2026-08-27Behavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-27
Weights batteryWeights forensics: no GPU, no downloadcomplete 2026-08-2732,000-token embedding scanned · 139 undertrained · pickle audit clean
Behavioral batteryLive-inference differentialsnot run

Ingot runs three batteries against a model. What each one checks →

Findings

Scanned 2026-08-27 · published from a community scan.

medium Pickle-serialized weights, no safetensors

Weights ship only as pickle-based files (pytorch_model-00001-of-00003.bin, pytorch_model-00002-of-00003.bin, pytorch_model-00003-of-00003.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 No license declared

The model card declares no license. You have no usage rights by default — treat as all-rights-reserved until the owner clarifies.

How to fix

Get a license from the owner or pick a licensed alternative — this is a legal gap, not a technical one.

  1. With no declared license you have no usage rights by default; treat the weights as all-rights-reserved.
  2. Open an issue or discussion on the repo asking the owner to declare a license, or use the licensed upstream/parent model instead.

medium Special token id outside the vocabulary

pad_token_id=-1 is outside the declared vocab_size of 32000. Runtimes either crash on it or silently ignore the setting (e.g. pad_token_id: -1), which breaks batching and stop handling.

How to fixingot patch

Align the stop-token declarations — a pure metadata fix to `generation_config.json` (and `config.json`).

  1. 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.
  2. Keep `config.json`'s `eos_token_id` consistent with (or a subset of) `generation_config.json`'s — runtimes differ in which file they read.
  3. For the pad-equals-EOS hazard: repoint `pad_token` at a dedicated padding token before fine-tuning; serving is unaffected.
  4. 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`).

low Undertrained tokens in vocabulary (non-ASCII tail)

Embedding-norm scan flagged 139 undertrained tokens (norm < 0.3× the vocabulary median), but 0 decode to plain-ASCII strings, so exposure in English-language pipelines is limited. 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-00003.bin, pytorch_model-00002-of-00003.bin, pytorch_model-00003-of-00003.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.

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 MBZUAI-LLM/LLaMA-7B-GLoRA-ShareGPT

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-27.

architecturellama · 32 layers · 4096-dim
vocabulary32,000 tokens
licensenone declared
serializationno safetensors pickle custom code
chat templatenone
glitch-token surface139 undertrained candidates, 0 plain-ASCII
Full measured fingerprint
architecturesLlamaForCausalLM
librarytransformers
pipelinetext-generation
repo files16 — pickle: pytorch_model-00001-of-00003.bin, pytorch_model-00002-of-00003.bin, pytorch_model-00003-of-00003.bin
revisiona7aa1cd44c24
HF snapshot12 downloads · 4 likes · updated 2023-11-18 · captured 2026-08-25
pickle auditpytorch_model-00001-of-00003.bin, pytorch_model-00002-of-00003.bin, pytorch_model-00003-of-00003.bin — 3 standard global(s)
embedding tensormodel.embed_tokens.weight · F32 · 32,000×4096
embedding normsmedian 1.3244 · mean 1.2835
lineage checkno claimed base model
Battery runs (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightscomplete2026-08-25 22:4436s1
weights run 2026-08-25 — measurements
probes runglitch-norm-scan, zero-template-token-scan, pickle-static-analysis, lineage-norm-correlation
probes skippedtoken-decode: no tokenizer.json
embedding tensormodel.embed_tokens.weight · F32 · 32,000×4096
glitch surface139 undertrained, 0 plain-ASCII
lineage checknot checked (no claimed base model)

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/MBZUAI-LLM/LLaMA-7B-GLoRA-ShareGPT/badge.svg)](https://ingot.tools/models/MBZUAI-LLM/LLaMA-7B-GLoRA-ShareGPT)
Gate it in CI