Model page

EarthSpeciesProject/NatureLM-audio warn

downloads 887likes 35license cc-by-nc-sa-4.0params 665.4Mupdated 2025-09-09

claims base: meta-llama/Llama-3.1-8B-Instruct · chat template: not found · view on Hugging Face ↗

Scan coverage

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

BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-21
Weights batteryWeights forensics — no GPU, no downloadcomplete 2026-08-21128,257-token embedding scanned · 752 undertrained · lineage consistent
Behavioral batteryLive-inference differentialsnot run

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 License differs from claimed parent (cc-by-nc-sa-4.0 vs llama3.1)

This model declares cc-by-nc-sa-4.0 while its claimed base meta-llama/Llama-3.1-8B-Instruct 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.

  1. 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.
  2. If the re-license is not permitted, the parent's terms govern your use regardless of what this repo declares.

medium Chat template dropped vs parent

meta-llama/Llama-3.1-8B-Instruct 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.

low Undertrained tokens in vocabulary (non-ASCII tail)

Embedding-norm scan flagged 752 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 Weights consistent with claimed parent meta-llama/Llama-3.1-8B-Instruct

Mean cosine similarity of 64 sampled token-embedding rows against meta-llama/Llama-3.1-8B-Instruct is 1.000 — the weights plausibly descend from the declared base (relation: unspecified).

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.

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.

parameters665.4M
vocabulary128,257 tokens
licensecc-by-nc-sa-4.0
serializationsafetensors custom code
chat templatenone
claimed lineagemeta-llama/Llama-3.1-8B-Instruct
lineage verifiedconsistent vs meta-llama/Llama-3.1-8B-Instruct — embedding-row cosine 1.000
glitch-token surface752 undertrained candidates, 0 plain-ASCII
Full measured fingerprint
repo files7
revision77855d9b0acd
HF snapshot893 downloads · 35 likes · updated 2025-09-09 · captured 2026-08-21
embedding tensorllama_embed_tokens.weight · BF16 · 128,257×4096
embedding normsmedian 0.6849 · mean 0.6713
lineage checkconsistent — cosine 1 over 64 sampled rows vs meta-llama/Llama-3.1-8B-Instruct

Battery runs

The run trace behind the findings above: every deep-battery job for this model, with what each run measured or why it failed. Findings are only as good as the runs that produced them.

batterystatusqueueddurationattempts
weightscomplete2026-08-21 05:1380s1
weights run 2026-08-21 measurements
probes runglitch-norm-scan, lineage-norm-correlation
probes skippedtoken-decode: no tokenizer.json
embedding tensorllama_embed_tokens.weight · BF16 · 128,257×4096
glitch surface752 undertrained, 0 plain-ASCII
lineage checkconsistent — cosine 1 over 64 rows vs meta-llama/Llama-3.1-8B-Instruct

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 EarthSpeciesProject/NatureLM-audio

Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the 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/EarthSpeciesProject/NatureLM-audio/badge.svg)](https://ingot.tools/models/EarthSpeciesProject/NatureLM-audio)
Gate it in CI