nomic-ai /nomic-embed-text-v1.5

Verdict

Held

There is not enough licence evidence to prove the licence, so it is not admitted.

What would change it: evidence from the licensor, or a human ruling. A hold is not a failure.

A verdict covers licence, provenance and files. Quality and fit on your own tasks are measured by Compare.

What was checked

  • Licence Not concluded

    Apache-2.0 is declared only as a repository tag (T3), which is not a grant.

  • Provenance Not verified

    The licensor's own repository.

  • Files Not verified

    Safetensors. The weights digest was not verified, so they are not claimed as byte-checked.

  • Export screening Not yet assessed

    No export claim is made.

Verify this verdict

Download attestation.json and check it against the published key:

python scripts/verify-verdict.py

Full record
Revision
e9b6763023c676ca8431644204f50c2b100d9aab
Date assessed
2026-09-23 BACKFILL
Upstream released
2026-04-07T14:17:02Z, the commit date of the assessed revision, recorded 2026-09-25. A reconstruction: this verdict was assessed before upstream release tracking began, so it is excluded from the median.
Release to verdict
Verdict latency: 4041 hours from the upstream release to 00:00 UTC on the assessment date. The record is dated, not timed, so the true figure may be up to 24 hours higher.
Provenance label
the weights digest was not verified for this verdict, so the weights are not claimed as byte-checked
Licence, declared and concluded
Declared: Apache-2.0 (as a repository-metadata-tag). Concluded: NoAssertion: no grant text exists to conclude from, so no licence is concluded for these weights.
Evidence tier
T3: a repository metadata tag only. Not a grant: the identifier is the publisher's assertion with no text behind it, so the record is held whatever the identifier says.
Deviation from canonical text
Not assessable: the repository ships no licence file, so there is nothing to compare against the pinned canonical text.
Added-clause screen
Run over the declared sibling policy files; none were declared for this model.
Provenance chain
Source: huggingface.co/nomic-ai/nomic-embed-text-v1.5. Official licensor repository: yes.
Base lineage
Not a derivative recorded in the admission record, so no base licence obligations arise.
Base-licence obligations
None recorded: this is not a derivative, or the base's conditions were not engaged.
Contradiction triage
None recorded.
Files and integrity
safetensors; the weights digest was not verified for this verdict, so the weights are not claimed as byte-checked.
Export screen
Export screening: not yet assessed. No export claim is made. The record carries status: not_assessed, basis: null, assessed_by: null, assessed_date: null, reference: null.
Declared training data
not recorded in the admission record.
What was checked
Canonical text pinned and digest-verified, identifier taken from the licensor's own repository metadata, added-clause screen run over sibling policy files, provenance chain recorded. The licensor's own licence file is not compared byte for byte on this evidence path.
Signed attestation
attestation.json: a DSSE envelope over an in-toto Statement v1, whose subject is the weights file digests and whose predicate is this record's provenance artefact. Signed with the key published at /verdicts/keys/, which states the fingerprint, the date the key came into use and how to verify the signature. Key custody: a local key on one operator host, not an HSM.
Gate findings
licence-evidence: incomplete licence evidence, not a licence verdict: evidence tier T3 (a repository metadata tag alone), so Class A is not proven whatever the declared identifier "Apache-2.0" says. Class A requires T1 or T2 (decision 0138 clause 4: a metadata tag is not a grant), so this holds for a human; ship a licence file (T1) or a full licence section in the model card (T2) and it re-evaluates. The gate's own words, with one term normalised; the signed attestation carries them exactly.

Running models like this in your own estate? Heliast runs the same gate inside your environment, on your policy.

Book a discovery session