Model page

Open-Bee/Bee-8B-RL warn

Loading it runs custom code from the repo; the chat template was dropped from its base model, which changes behavior; its architecture doesn't match its claimed base model.

downloads 82.4klikes 79license apache-2.0arch Beeparams 8675.0Mupdated 2026-03-10

claims base: Qwen/Qwen3-8B · chat template: present · view on Hugging Face ↗

Scan coverageStatic battery2026-08-21Weights batteryfailedBehavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-21
Weights batteryWeights forensics — no GPU, no downloadfailed429 Too Many Requests for https://huggingface.co/api/models/Open-Bee/Bee-8B-RL
Behavioral batteryLive-inference differentialsnot run

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

Findings

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

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 Chat template dropped vs parent

Qwen/Qwen3-8B 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.

  1. Run `ingot patch <owner/model>` — the patch manifest carries the parent's template and applies it to a local copy's `tokenizer_config.json`.
  2. 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.
  3. 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.

medium Architecture differs from claimed parent (Bee vs qwen3)

This model declares Qwen/Qwen3-8B as its base, but its config declares architecture 'Bee' while the parent is 'qwen3'. A finetune, merge, or quantization cannot change the architecture family — the lineage label is wrong or misleading, so treat provenance claims (training data, safety posture, licensing) as unverified.

How to fix

Fix or verify the `base_model` declaration so lineage checks can run.

  1. If you own the repo: correct the `base_model` field in the model card metadata to the real, public parent.
  2. If you don't: identify the true parent (config architecture + weight shapes narrow it fast) and re-scan with that lineage in mind.

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 Open-Bee/Bee-8B-RL

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

architectureBee
parameters8675.0M
licenseapache-2.0
serializationsafetensors custom code
chat templatenone
claimed lineageQwen/Qwen3-8B
lineage verifiedunverified — weights battery pending
Full measured fingerprint
architecturesBeeForConditionalGeneration
librarytransformers
pipelineimage-text-to-text
repo files25
revisionb988b91d4c84
HF snapshot118.2k downloads · 79 likes · updated 2026-03-10 · captured 2026-08-21

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/Open-Bee/Bee-8B-RL/badge.svg)](https://ingot.tools/models/Open-Bee/Bee-8B-RL)
Gate it in CI