Know the licence of everything you ship
Audited 644 Rust crates for licence compatibility on every build,
and proved the check fires by rewriting one crate's licence and by
moving the pinned core revision without regenerating.
September 2026

Situation. Linking a Rust core into a shipped application means
shipping everything that core depends on. The dependency graph is
644 crates. Each carries a licence, some carry more than one, and a
single copyleft crate arriving three levels down through a routine
version bump changes what the application as a whole may be
distributed under — silently, in a lock file nobody reads line by
line.

Task. The licence position had to be verified on every build rather
than reviewed once, with an explicit allow list, so that a change in
the graph is a build failure and not a discovery made later by
someone else.

Action. The audit resolves the full transitive graph and checks each
crate's licence expression against a list of terms the project
accepts, evaluating the boolean expressions properly — a crate
offering a choice of two licences is acceptable if either is on the
list, and a crate requiring both is only acceptable if both are.
Anything unmatched fails the build rather than warning, and adding a
term to the allow list is a deliberate edit with a reason. A check
that has never failed is indistinguishable from one that cannot
fail, so it was made to fail on purpose, twice. Once by rewriting a
crate's licence expression to something the list does not accept,
which is the shape of a crate changing its terms upstream between
versions — the case no human review catches, because the crate
itself is not new. Once by moving the pinned core revision without
regenerating the audit, which is the shape of a core bump quietly
bringing a new dependency with it. Both provocations failed the
build as intended, and the check was left in place rather than
widened.

Result. The distribution position is checked on every build, and the
check is known to work because it was made to fail rather than
because it has never spoken. Before it existed, the bundle, the
licence file and the project's own README all made a claim about 644
crates that nothing had verified. The limit is precise and should
not be overstated: the check reads the declared licence metadata,
and metadata can be wrong or incomplete. It proves nothing about a
crate that misdeclares itself, and it is not legal advice.

Categories:
1Data Governance	/categories/data-governance/	data.engineer.company	70
1DevOps	/categories/devops/	data.engineer.company	70
1Automation & CI/CD	/categories/automation/	data.engineer.company	70
1Security	/categories/security/	data.engineer.company	70
1Documentation	/categories/documentation/	data.engineer.company	70

Services:
1Data Governance & Quality	/services/data-governance/	data.engineer.company	70
1DevOps & CI/CD Automation	/services/devops-cicd/	data.engineer.company	70
1Security & Access Management	/services/security-access/	data.engineer.company	70

hThis page on the web	URL:https://data.engineer.company/portfolio/know-the-licence-of-everything-you-ship/	data.engineer.company	70
