Skip to content
CLEARANCE
Illustrative example · generated from a synthetic sample project

A worked example, not an audit.
One sample project, four verdicts.

Not because the licences in this sample are exotic. Because in four of the five blocked findings here, the obligation that blocks the build is written in a document the code licence never points to — the weights licence, the platform terms, or a reserved mark.

This is not a study. Clearance generated the report below from a synthetic project, so that you can see the shape of the output before running it on your own code. No real repository was audited, and nothing on this page is a claim about the software industry.

The sample at a glanceillustrative sample
5
Blocked outright
4
Conditional
3
Undetermined
2
Clean
Blocked or undetermined8 of 14
Trap invisible to a code-only scanner4 of 5
Dependencies with weight files6 of 14
Intent modelled for every finding: commercial, closed-source, network-exposed, unmodified. One intent, applied uniformly, so the verdicts compare.

01

Five findings

Five findings from the sample, each one checkable against the table below. The counts describe this synthetic project and nothing wider — they illustrate the output, they are not a survey.

4
of 5
The trap was invisible to a code-only scanner

In four of the five blocked findings, the code licence permitted exactly what the builder intended to do. The block came from the weights licence, the platform terms, or a reserved trademark. A scanner that reads only code returns a pass on all four.

2
of 6
Two of the six weight-bearing findings stated no weights licence at all

Six dependencies in the sample ship model weights. Two of them stated no licence for those weights in config.json, a model card, or a sibling LICENSE. Under any honest analysis these are not "clean" — they are UNDETERMINED, and a tool that reports them as passing is inventing a fact.

2
findings
Code-licence and weights-licence divergence, twice

Two findings were permissively licensed at the code level and loaded weights under a non-commercial or gated licence. It is the AI-era trap a code-only scan cannot see: the two layers disagree, and only one of them is in the lockfile.

Apache-2.0 code + CC-BY-NC weights Apache-2.0 code + research-only weights
2
findings
Reserved brand assets, stated outside the licence file

Two findings grant the code freely and reserve the name, logo or icon in a separate trademark notice. A fork is required to rebrand — an obligation that never appears in the LICENSE file and therefore never appears in a licence report.

1
finding
Ambiguity was real, not an artefact of the tool

One finding had a clause that genuinely supports two readings — a community licence whose commercial gate reads "fewer than N users, or twelve months, whichever is later". Both readings were recorded. Pretending one is certain would have been the dishonest answer, and would have produced a confident wrong verdict in a case where the user needed to know they should ask a lawyer.


02

Where the traps sat in this sample

The distribution is the point. Twelve of the fourteen findings are not clean, and only one of those twelve is blocked by the code licence.

Blocking layer — findings affected
Model-weights licence
5
Reserved brand assets
2
Code licence (copyleft)
1
Platform terms (upstream CLI)
1
Territorial clause
1
Attribution only
1
Terms in an unreadable document
1

Each finding in the sample is blocked by exactly one layer, so these sum to the twelve findings that are not clean. Five of them are the weights licence, and the code licence accounts for one.

Code licence across the sample's fourteen dependencies
MIT
6
Apache-2.0
6
BSD-3-Clause
2

Every dependency in the sample is permissively licensed at the code level. That is precisely why a code-only scan of this sample produces a false sense of safety: the code licence is what blocks exactly one of the fourteen findings.


03

Method

This is the method Clearance runs on every scan. Here it was applied to a synthetic project, so the verdicts below show the shape of the output rather than reporting on anyone's code.

The intent modelled

One intent, applied uniformly to every dependency in the sample, so the verdicts compare:

commercialtrue
licence_modelclosed-source
modifiedfalse
network_exposedtrue
distributedfalse
saastrue

This is the intent modelled for the sample: a hosted service, sold, closed-source, not modified. Every verdict below was reached under it, and only it — a report using a weaker intent would flatter the sample and be useless.

Procedure, per dependency

  1. Resolve dependencies from the committed lockfile; fall back to the manifest only where no lockfile exists.
  2. Read the code licence from the vendored licence file where present, and from package metadata otherwise.
  3. Identify weight files by magic bytes. Resolve their licences from GGUF metadata, config.json, model-card frontmatter and sibling licence files.
  4. Compare the code licence against the weights licence and record any divergence.
  5. Read trademark and brand-asset notices for reserved marks.
  6. Detect orchestration of third-party CLIs and read the relevant platform terms.
  7. Evaluate every obligation against the modelled intent, and record a confidence level for each.
What this report is not
×It is not a legal opinion, and it is not legal advice.
×It is not a claim that any project is infringing. Each verdict is a statement about whether one commercial intent is compatible with the published terms.
×It is not a quality judgement. A DO NOT SHIP verdict says nothing about whether the software is any good.
×It is not a study. The project behind the table is synthetic, and no count on this page measures anything in the real world.
Corpus provenance
Corpus version
2026.09.2
Schema
1
Licences
12
Obligations
39
Traps
12
Terms of service
6
Territories
4
Citations
82
Signature
Ed25519 verified
Licence
CC-BY-4.0

The sample was produced with corpus 2026.09.2, which is signed and verified on every load. When a later corpus changes a verdict, the changelog records it rather than editing the report quietly.


04

Raw data

Every finding carries the layer that blocked it, a verdict and a confidence level. The names here are placeholders, because the sample is synthetic — there is no real repository behind them to accuse of anything.

14 findings · synthetic sample illustrative output, not a real dataset
Repository Verdict Code licence Weights Blocking layer Conf.
owner/crawler-kitDo not shipMIT—code · AGPL depHigh
owner/voice-cloneDo not shipApache-2.0CC-BY-NC-4.0weights · NC clauseHigh
owner/pdf-agentDo not shipMIT—brand · reserved marksMed
owner/vision-ggufDo not shipApache-2.0research-onlyweights · research onlyHigh
owner/scrape-flowDo not shipBSD-3-Clause—platform · automation banHigh
owner/tts-liteConditionalApache-2.0Apache-2.0attribution onlyHigh
owner/agent-memConditionalMIT—brand · rebrand requiredMed
owner/speech-cmConditionalMITCommunity v2weights · MAU gateMed
owner/ocr-pipeConditionalApache-2.0—territory · prior applicationHigh
owner/vector-liteShipMIT——High
owner/schema-toolShipApache-2.0——High
owner/whisper-ggufUndeterminedMITnot foundweights · no licence statedLow
owner/embed-batchUndeterminedApache-2.0not foundweights · no licence statedLow
owner/img-tagUndeterminedBSD-3-Clause—terms in an unreadable PDFLow

The names in this table are placeholders. A report over a real project names the repository, and every finding carries the file and line of the clause it cites.


What this means for you

The verdict is not the point.
The citation is.

The sample above is invented; the shape of it is not. A builder making licence decisions by intuition is not being careless — they are being asked to do a job nobody gave them the documents for, and the documents are the part nobody hands over. The fix is not more diligence. It is a build step.

WORKED
EXAMPLE
NOT AN AUDIT

Every verdict in the sample came out of the corpus named above, signed and verified on load. When a later corpus changes a verdict, the changelog records it rather than editing the report quietly.

Informational findings based on the licence text as published on the date recorded in the corpus. This is not legal advice. Ambiguous clauses are flagged as ambiguous and carry a confidence level. Important decisions must be reviewed by a qualified professional. No repository named in this sample is accused of infringing any licence; each verdict is a statement about the compatibility of the published terms with one specific commercial intent.