Open source licensing and compliance standards
Criteria verified as of August 2026. Re-verify on the web before committing to anything (§8).
1. Scope and triggers
The licence is an engineering constraint, and it is verified at the moment the dependency is
added — not when the customer turns up asking. An incompatible licence discovered in a
two-year-old git log is not a legal finding: it is an architectural debt that is already
in production, in the customer's installer and in the image you signed. Checking it costs
seconds in the PR; discovering it in due diligence costs a redesign.
Operational corollary, and it is the entire thesis of this document: the gate goes in the PR
that adds the dependency. A quarterly scan of the whole tree produces reports; a gate in the PR
produces decisions. If you can only have one, have the gate.
Scope notice — this is NOT legal advice. What is here is engineering and compliance
criteria: what gets verified, what breaks the build, what gets recorded and who approves an
exception. The interpretation of a clause, the assessment of contractual risk and any
decision with legal exposure are referred to qualified legal counsel — notably: strong
copyleft entanglement in a distributed product, obligations under a vendor contract,
non-compete clauses of source-available licences, ownership of an employee's or contractor's
work, and any response to a compliance claim. This document says when you have to ask a
lawyer; it does not answer for one.
Covers: what is and is not open source (the OSI's OSD and the source-available /
fair-source debate); licence families and what they actually require; compatibility and the
direction of combinations; the distinctions that cause almost every mistake (static vs. dynamic
linking, distribution vs. internal use, container vs. binary, SaaS); SPDX as the canonical
identifier; SBOM and its real regulatory obligation; the process: policy, CI gate,
scanning, inventory, exceptions and attribution; what to do when a dependency
relicenses; contributing outwards (CLA vs. DCO); and the licence of models, datasets and
content.
Triggers: LICENSE, LICENSE.md, LICENSE.txt, COPYING, NOTICE, LICENSES/,
REUSE.toml, .reuse/dep5, THIRD-PARTY-NOTICES, deny.toml, .licenserc,
dependency-review-action, allow-licenses, deny-licenses, cargo deny check licenses,
go-licenses, pip-licenses, liccheck, license-checker, reuse lint, scancode,
FOSSology, ORT (.ort.yml, evaluator.rules.kts); SPDX identifiers (MIT,
Apache-2.0, MPL-2.0, GPL-3.0-or-later, AGPL-3.0-only, LGPL-3.0-only, EPL-2.0,
CDDL-1.0, BSD-3-Clause, WITH LLVM-exception, LicenseRef-*); SPDX expressions
(AND, OR, WITH); source-available (BUSL-1.1, ELv2, SSPL, RSALv2, PolyForm, FSL, FCL,
MSCL); SPDX-License-Identifier: in a file header; SBOM (bom.json, *.spdx.json,
CycloneDX, syft, trivy sbom); CRA; CLA, DCO, Signed-off-by:; relicensing, forking.
This skill is the CROSS-CUTTING OWNER of the subject
Every skill in the catalogue verifies the licence of the tools it pins — and several have
done so and found surprises (§3.6). That is right and must continue. But the licence policy,
the gate that enforces it and the exception process live HERE, and only here. A language
skill decides which linter to use; it does not decide whether AGPL is acceptable in the
product. If another catalogue skill contradicts the policy of §5.1, this one wins.
Precedent that justifies the procedure in §6, verified in this series: in YottaDB the
file called LICENSE does not contain the licence —it is explanatory copyright text—; the
real licence (AGPLv3) is in COPYING. And GnuCOBOL is GPLv3 in the compiler but
LGPLv3 in the runtime, with the added trap that its ISAM backend via Berkeley DB drags in
Oracle conditions. Operational consequence: it is not enough to read the file called
LICENSE; you have to read the one that contains the licence, and check whether compiler and
runtime go separately.
Variants of the same failure, all confirmed in the catalogue — any mechanical check
that assumes raw.../main/LICENSE produces false negatives: file with another name
(COPYING in YottaDB), another extension (LICENSE.txt in NetBox, LICENSE.md in Traefik),
another capitalisation (License.txt in Lucee, license.txt in BoxLang) and another default
branch (master in Angie, 7.0 in Lucee, development in BoxLang). And an extra warning:
GitHub's automatic licence classification gets it wrong — it marks BoxLang as
NOASSERTION because it carries a commercial preamble in front of a perfectly valid
Apache-2.0 text. The API is not a substitute for reading the file.
Not applicable: see vulnerability-management-standards (thin and reciprocal boundary: the same
SBOM serves both and that is why they get confused. The SBOM is generated once and consumed
twice: for CVEs —triage, EPSS/KEV, VEX, patching SLA— theirs; for licence
obligations —what I may combine, what I must publish, what I must attribute— belongs here.
Rule: if the question is "can this compromise me?", it is theirs; if it is "does this oblige me to
anything?", it belongs here), cicd-standards (the pipeline runs the gate: the runner, the job,
the cache, the OIDC and the artifact signature are theirs; the threshold, the allowlist and what
breaks the build belong here), grc-compliance-standards (the corporate regulatory framework, the
risk register, the formal acceptance and the audit evidence are theirs; here the technical control
that feeds them and the licence inventory), secrets-management-standards (a commercial licence
key —Directus, gitleaks-action— is a secret and is managed there; that you need one is a
licence fact and belongs here), appsec-standards (vulnerability classes
and SAST/DAST selection; that Brakeman is not free belongs here), ai-governance-standards
(the governance of AI use —system inventory, AI Act, impact assessment— is
theirs; the licence of the artifact —weights, dataset, provider terms of use— belongs here),
ai-agent-workflow-standards (already written: the licence and authorship of code generated by an
agent is declared there as an UNRESOLVED question. That is respected: this skill does not invent
an answer, it only fixes the procedure of §6.4 —traceability and provenance
verification— which is valid regardless of how it gets resolved), git-workflow-standards
(the repository's licence file, the Signed-off-by and the commit signature are
theirs; which licence to put and why to require DCO instead of CLA belongs here), and the language
skills —python-standards, go-standards, rust-standards, typescript-standards,
java/jvm-spring-standards, etc.— (the specific package manager, its lock file
and its ecosystem's scanning command are theirs; the policy that command applies belongs
here). With green-it-standards: the licence of carbon measurement tools is
governed by this skill. Here only the free licence: the proprietary commercial licence and
the vendor audit —named user, indirect access, annual measurement and declaration—
belong to erp-sap-standards and crm-salesforce-standards.
2. Default decisions
Verify the latest version on the web before pinning it in a real project (§8).
| Area |
Default |
Reason / justifiable alternative |
| Licence of what you publish (library) |
Apache-2.0 |
It is the permissive one with an explicit patent grant (§3.2). MIT/BSD-3 only if the ecosystem imposes it (npm, Go). In Rust, the idiom is Apache-2.0 OR MIT — the OR exists precisely to provide a way out of the GPL-2.0 incompatibility |
| Licence of an internal, non-distributed application |
Proprietary / no public licence |
Not publishing is not an oversight; publishing without deciding to is. A repo with no LICENSE is not open source: without an express grant, all rights are reserved by default |
| Identifier |
SPDX expression in LICENSE, in the package metadata and in the header (SPDX-License-Identifier:) |
The only format a gate can parse. Free prose = manual review |
| Licence list |
SPDX License List — verify the current version (§8) |
It is the gate's vocabulary. Anything unlisted goes as LicenseRef-... and enters manual review by definition |
| SPDX specification |
3.0.1 (Dec 2024) as the published version; 3.1 in release candidate since Jan 2026 |
Do not confuse the specification version (3.0.1) with the list version (3.x independent, at 3.28.0 as of Feb 2026). Verify both separately (§8) |
| SBOM format |
CycloneDX for internal consumption; SPDX when the customer or regulator requires it |
Verify the version your consumer accepts before generating: some consumers reject the latest minor. This version criterion is coordinated with vulnerability-management-standards |
| SBOM generation |
Syft (or trivy sbom) in the build pipeline, over the artifact, not over the repo |
The repo's SBOM does not describe what you deploy. Verify the tool's licence and status (§8) |
| Licence detection (deep) |
ScanCode Toolkit (Apache-2.0) |
Scans the actual text of files, not the manifest. It is the only way to detect the cases in §3.6 |
| Clearance and review workflow |
FOSSology (GPL-2.0) if there is a formal audit obligation |
Verify the tool's licence before integrating it into a product: FOSSology is strong copyleft, which is irrelevant for using it and relevant if you embed it |
| CI orchestration |
ORT (OSS Review Toolkit), Apache-2.0 |
Runs ScanCode + evaluates against your policy + generates attribution. It is the only one on the list that does all three. Cost: it is a project in itself |
| PR gate (GitHub) |
dependency-review-action with allow-licenses — never deny-licenses |
deny-licenses is deprecated and slated for removal in the next major. And the underlying argument is correct: a list of forbidden ones will always forget one (the classic: you forbid GPL-2.0 and CC-BY-SA-4.0 comes in). Allowlist or no gate |
| Per-ecosystem gate |
The native tool: cargo-deny (Rust), go-licenses (Go), pip-licenses/liccheck (Python), license-checker (npm), dependency-license-report (JVM) |
dependency-review-action only sees the dependencies that change in the PR; the native gate sees the whole graph. You need both, and both as required status checks |
| Authorship marking in the repo |
REUSE (LICENSES/, SPDX-License-Identifier headers, reuse lint in CI) |
Verify the current version of the specification (§8; there was 3.3 from Nov 2024 with signs of a later 3.4 — declare the discrepancy, see §8). Practical warning: GitHub identifies the licence with licensee, which does not understand REUSE — leave a LICENSE at the root as well as the directory |
| Attribution when distributing |
THIRD-PARTY-NOTICES.txt generated in the build, versioned alongside the artifact |
Generated, not hand-written: a manual file is out of date on day 2. See §5.4 |
| Incoming contributions |
DCO (Signed-off-by:) |
Less friction and sufficient for most projects. CLA only if you need to relicense or sell exceptions — and then say out loud that that is the reason (§6.1) |
3. What open source is, what it is not, and what each family requires
3.1 The definition and the edge
The Open Source Definition (OSI) opens, verbatim:
«Open source doesn't just mean access to the source code. The distribution terms of
open source software must comply with the following criteria:»
and lists ten criteria, whose titles are, verbatim: Free Redistribution; Source
Code; Derived Works; Integrity of The Author's Source Code; No Discrimination Against
Persons or Groups; No Discrimination Against Fields of Endeavor; Distribution of License;
License Must Not Be Specific to a Product; License Must Not Restrict Other Software;
License Must Be Technology-Neutral. The document identifies itself as «Version 1.9, last
modified, 2007-03-22».
Hard rule: criterion 6 (No Discrimination Against Fields of Endeavor) is the one that
rules out almost everything source-available. A clause saying «you may not offer this as a
competing service» or «not for commercial use» discriminates against a field of endeavour and
therefore is not open source, however much the repository sits on GitHub and says «open» on the front page.
Status as of Aug 2026 of the licences that cause the most confusion — none approved by the OSI:
| Licence |
What it is |
Note |
| SSPL-1.0 |
source-available, copyleft extended to the service stack |
MongoDB withdrew it from the OSI submission in 2019; in Jan 2021 the OSI declared that it does not meet the OSD because it discriminates against fields of endeavour, and called it «fauxpen» source |
| Elastic License 2.0 (ELv2) |
source-available, forbids offering it as a managed service |
Elastic itself describes it as not OSI-approved |
| BUSL-1.1 / BSL |
non-compete + deferred conversion to open source (4 years by default) |
«BSL is not an OSI approved license» — statement by Elastic itself. The Additional Use Grant is variable per project: you have to read the one for the specific project, not «the BUSL» |
| RSALv2 |
Redis's source-available |
— |
| PolyForm Shield / Noncommercial / Perimeter |
source-available with an anti-competition or non-commercial clause |
— |
| FSL (Functional Source License) |
fair source: non-compete + conversion to Apache-2.0 or MIT after 2 years |
Created by Sentry as a simplification of the BUSL, fixing its variables |
| FCL (Fair Core License) |
variant of FSL «that includes license key support» (fair.io, verbatim) |
Adds limitations derived from ELv2 |
| MSCL (Monospace Sustainable Core License) |
derived from FCL, used by Directus v12 |
See §3.6 |
Fair Source is defined around three conditions: publicly readable code, use /
modification / redistribution with minimal restrictions, and delayed open source publication
(DOSP). fair.io recognises, verbatim: FSL («A simple non-compete license with
eventual Open Source conversion after two years»), FCL («A variant of FSL that includes
license key support») and BUSL/BSL («A complex non-compete license with eventual Open Source
conversion after a certain amount of time, usually four years»). Fair source is not open
source and does not claim to be; the conflict is one of nomenclature, not of honesty.
Declared discrepancy: the OSI itself is the source of the concept of Delayed Open Source
Publication that underpins the fair source designation, and at the same time members of its board
publicly hold that these licences are not open source because their freedoms do not
reach everyone and non-compete is «legally fuzzy». Both things are true at
once: the OSI recognises the mechanism (DOSP) and rejects the label. Do not cite one without the other.
Operational consequence of deferred conversion — and almost nobody exploits this: in a
licence with DOSP, each specific version has its own conversion date. Akka moved to
BSL in 2022 and its versions revert to Apache-2.0 36 months after their publication;
Akka 2.7.0 has already reverted. Rule: a licence with DOSP is not evaluated as a licence, it is evaluated
as a calendar — record in the inventory the version, its publication date and its
conversion date, because the answer changes over time without anyone touching anything.
3.2 Families and what they actually require
Permissive — MIT, BSD-2/3-Clause, ISC, Apache-2.0. They require preserving the copyright
notice and the licence when redistributing. That is already a real obligation and it is the most
breached one (§5.4). The technical reason to prefer Apache-2.0 over MIT is not copyleft: it is the
express patent grant and its termination clause —if you sue a user of the software over
patents, you lose the patent licence—. MIT and BSD are silent on
patents, and silence is not a grant. Apache-2.0 additionally adds the NOTICE file
obligation: if the project ships one, you propagate it.
Weak copyleft.
- LGPL (2.1 / 3.0): the copyleft reaches the library, not your application, on condition
that the end user can replace the library with another version. With dynamic linking
that is trivial; with static linking it requires delivering objects or sources that allow
relinking. LGPL-3.0 additionally adds the anti-tivoization clause inherited from GPL-3.0.
Real precedent from the catalogue: Pa11y is LGPL-3.0, not MIT.
- MPL-2.0: the copyleft is per file, not per project. You modify a covered
.js →
that file remains MPL and you publish that modified file. Your new code in new files
is not contaminated. This makes it suitable for combining with proprietary code, and it is the
reason so many development tools choose it. Real precedents:
axe-core, StyLua, selene, Lightning CSS and data.table are MPL-2.0; OpenBao too.
- EPL-2.0: copyleft at «module» scope, with source availability obligations and its own
patent clause. Fine point: EPL-2.0 allows designating the GPL as a secondary licence
— if the project has done so, the compatibility answer changes. Read it in
the file, do not assume it.
Strong copyleft.
- GPL-2.0 vs. GPL-3.0: they are not the same decision. GPL-3.0 adds anti-tivoization
(an obligation to deliver installation information on consumer hardware), an express
patent grant and compatibility with Apache-2.0.
GPL-2.0-only and GPL-2.0-or-later are
different licences and the gate must distinguish them: -or-later lets you move up to 3.0 and
resolve incompatibilities; -only does not. Real precedent: perltidy is GPL-2.0.
- AGPL-3.0 — the «network use» trigger, and it is the one that kills a SaaS. GPL requires delivering
sources when distributing; AGPL additionally requires offering the Corresponding Source to
users who interact with the program over a network, even if you never distribute a
binary. This turns «we do not distribute, therefore it does not apply to us» —the correct reasoning
for GPL in a SaaS— into a falsehood. The scope is the modified program and its Corresponding
Source, not your whole stack (that is SSPL, and that is why SSPL is not open source). Real
precedents: k6, Pyroscope, Slither, Echidna and Medusa are AGPL-3.0; and Elasticsearch (2024) and
Redis 8 (2025) returned to the OSD via AGPL, precisely because it deters resale
as a service without leaving the definition.
- CDDL-1.0 — it turns up where nobody expects it. Per-file copyleft (like MPL-1.1, from which
it descends) and considered incompatible with the GPL by the FSF, among other things because of its
jurisdiction clauses. It is the reason for the eternal ZFS-in-the-Linux-kernel problem.
Real precedent from the catalogue: FlameGraph is CDDL, and it shows up in any
profiling workflow without anyone looking at it.
Exceptions (WITH). An SPDX exception changes the result: Apache-2.0 WITH LLVM-exception (Wasmtime, and the whole LLVM ecosystem) exists precisely to avoid
attribution obligations in linked binaries and to ease combination. Treating
Apache-2.0 WITH LLVM-exception as plain Apache-2.0 is an analysis error, not a
nuance. The gate must understand the WITH operator; if your tool collapses it, you have a
false result and you do not know it.
3.3 Compatibility: it is directional, not symmetric
The right question is never «are A and B compatible?», but «under which licence does the
combined work end up, and can I accept it?». Compatibility has a direction of travel:
- Apache-2.0 → GPL-3.0: they combine, and the result is GPL-3.0. Not the other way round: the
GPL-3.0 code cannot go into an Apache project.
- Apache-2.0 ↔ GPL-2.0-only: incompatible. The FSF holds that all versions of
the Apache License are incompatible with GPL v1 and v2, because of the patent and
indemnity clauses. This is the most common and most silenced conflict in the real ecosystem, and the
reason Rust is published as
Apache-2.0 OR MIT (you pick MIT and the problem disappears)
and why LLVM drafted its exception.
- MPL-2.0 → GPL/LGPL: MPL-2.0 was explicitly designed to be compatible (unlike
MPL-1.1), unless the project has marked the file as Incompatible With Secondary
Licenses. That notice is in the file header: if you have not read it, you have not verified
compatibility.
- CDDL ↔ GPL: incompatible according to the FSF.
- Permissive → proprietary: always possible, with the attribution obligation intact.
Gate rule: compatibility is not reasoned about in the PR, it is decided once in the
policy of §5.1 and the PR only checks membership of the list. Reasoning about compatibility in every
PR guarantees that one day it will be reasoned badly, in a hurry, on a Friday.
3.4 The four distinctions that cause almost every mistake
- Static vs. dynamic linking. Determines whether LGPL requires you to allow relinking
(§3.2). A Go binary is always static: in Go, «we link dynamically» is not an
available option and that argument does not exist. A
FROM scratch container with a
static binary inside does not save you either.
- Distribution vs. internal use. Classic copyleft (GPL, LGPL, MPL, EPL) triggers on
distributing, not on using. GPL software used internally and never delivered to a third party
creates no obligation to publish. That reasoning is correct and AGPL voids it (§3.2)
— and so does a customer to whom you deliver a virtual machine, a
.deb, an
image or a device.
- Container vs. binary. Delivering a container image is distribution of everything
inside it: the base image, its system packages and its libraries, not just your
application. Your source-code SBOM does not cover that. That is why the SBOM is generated from the
artifact (§2). A base image with a GPL package you do not invoke is still distribution
of that package.
- Does a SaaS distribute? Under GPL/LGPL/MPL, the default operational answer is no: giving
access to a service is not delivering copies. Under AGPL, yes in practice: the
obligation towards network users is triggered. And there are two frequent leaks that break «we do not
distribute»: the code you send to the user's browser (your JavaScript bundle is
distributed, to each and every one) and any agent, CLI or SDK the customer installs.
A backend that does not distribute with a frontend that does is the normal case, not the
exception.
3.5 SPDX and the file
Canonical identifier, in three places and all three mandatory when you publish:
LICENSE/LICENSES/ with the full text; the manifest's licence field with the
SPDX expression; and SPDX-License-Identifier: <expr> in the header of every file
(REUSE). Expressions: AND (you comply with both), OR (you pick one — and you must record which one
you pick, because Apache-2.0 OR MIT with no declared choice is a pending decision), WITH
(exception). Anything without a listed identifier goes as LicenseRef-... and enters
manual review by definition — a LicenseRef or a NOASSERTION is never self-approved.
3.6 Why the manifest's license field LIES
This section is the core of the skill and its reason for existing. During the construction of
this catalogue, verifying the raw LICENSE file, the following cases turned up —
all with third-party documentation claiming the opposite:
| Case |
What almost everyone says |
What the file says |
| Brakeman |
«MIT, it is the standard Rails scanner» |
Brakeman Public Use License, proprietary to Synopsys. Code prior to 15-Jun-2018: MIT. Later: not free. Scanning your own code is permitted; embedding it in a commercial product or service requires a commercial agreement. Free fork of the pre-acquisition code: Railroader |
| Directus |
«open source headless CMS» |
Since v12 (May 2026): Monospace Sustainable Core License, derived from FCL. Free commercial use only via Open Innovation Grant, capped at <$5M annual revenue and <50 employees; conversion to GPLv3 after 4 years; mandatory software key (goodbye honour system). The SDKs remain MIT. The package and the product do not share a licence |
| WebPageTest |
«open source web performance tool» |
PolyForm Shield: source-available with an anti-competition clause |
| FlameGraph |
«profiling script, MIT for sure» |
CDDL — incompatible with GPL (§3.2) |
| k6, Pyroscope |
«open source» (true) |
AGPL-3.0 — true and relevant if you embed them in a service |
| Slither, Echidna, Medusa |
«Trail of Bits tools» |
AGPL-3.0 |
| Pa11y |
«MIT like the rest of npm» |
LGPL-3.0 |
axe-core, StyLua, selene, Lightning CSS, data.table |
«MIT / permissive» |
MPL-2.0 (per-file copyleft) |
| perltidy |
— |
GPL-2.0 |
| Playwright |
— |
Apache-2.0 (not MIT) |
| Extism |
— |
BSD-3-Clause |
| Wasmtime |
«Apache-2.0» |
Apache-2.0 WITH LLVM-exception — the exception changes the analysis (§3.2) |
| Tolgee, Strapi |
«open source» |
Dual, with a proprietary ee/ directory in the same repository. The repo has one licence; parts of the repo have another |
| gitleaks |
«MIT» |
The scanner is MIT and its author declared it feature complete (security patches only; successor: Betterleaks). The GitHub action gitleaks-action is proprietary since v2.0.0 and requires a licence key to scan an organisation's repositories (free via form, with paid tiers by number of repos). Two artifacts, two licences, same name |
| Infracost |
«Apache-2.0, free» |
The CLI is Apache-2.0; the hosted pricing API it depends on has a quota and a paid plan. Free licence ≠ free operation |
| Akka |
«Apache-2.0» |
BSL since 2.7.x (2022), with a commercial threshold declared in the region of ~$25M revenue and automatic reversion to Apache-2.0 after 36 months per version. Fork: Apache Pekko (from 2.6.x, graduated at the ASF) |
| Vault |
«open source» |
BUSL since 2023. Fork: OpenBao (MPL-2.0, Linux Foundation) |
| Trivy |
«Apache-2.0 as always» |
It changed licence — verify the one for the artifact and version you use (§8) |
| Elasticsearch |
«it went back to being open source» |
It added AGPL-3.0 (2024) alongside SSPL and ELv2 for the source code. Open gap: the licence of the binaries distributed by Elastic — there are signs that the releases remain under the Elastic License even though the source is triple-licensed. Not closed here: see §8 |
The five rules that follow, and they are the policy:
- The manifest's
license field is a declaration by the packager, not a verified
fact. You read the LICENSE file of the specific version you are going to use.
- A repository may have more than one licence. The
ee/, enterprise/ or
pro/ directory is the standard open core pattern; the root manifest does not reflect it.
- A project may have more than one artifact with different licences (gitleaks vs.
gitleaks-action; Directus core vs. SDK; Elasticsearch source vs. binary). The unit of
analysis is the artifact you install, not the project that publishes it.
- The licence is tied to the version. «X is MIT» is a meaningless statement without a version.
- Free licence ≠ free to operate (Infracost) and free licence ≠ maintained
(gitleaks). Verify all three things: licence, operating cost and project status.
4. Gate quality: what gets checked and what breaks the build
In increasing order of cost. The first three are mandatory; the fourth depends on whether you
distribute.
- Precondition — lock file. Without
uv.lock / package-lock.json / go.sum /
Cargo.lock / poetry.lock the graph is not deterministic and any scan describes a
resolution that will never happen again. Without a lock there is no gate: there is theatre.
- PR gate (seconds).
dependency-review-action with allow-licenses. Fails if the
new dependency brings a licence outside the allowlist. Practical note: OTHER is not
a valid SPDX identifier and translates to LicenseRef-clearlydefined-OTHER — use it in
that form in the list or you will get false greens.
- Full-graph gate (minutes, on every
main build). The ecosystem's native tool.
It breaks the build. Specific warning: cargo-deny removed deny, copyleft,
allow-osi-fsf-free and unlicensed — now everything is denied except what is explicitly
allowed, which is exactly the right model; an old deny.toml with those fields
fails with an error, it does not degrade silently. And check the scope: by default it excludes
dev-dependencies and includes build-dependencies, because those do influence the
artifact.
- Deep text scan (nightly or per release). ScanCode/ORT over the artifact.
It is the only one that detects files with a header different from the project's, copied code and
ee/ directories. It does not block the PR; it opens a ticket with an SLA.
reuse lint if you publish: fails if any file lacks licence information.
What breaks the build (non-negotiable):
- ❌ Licence outside the allowlist (§5.1).
- ❌ Unknown licence,
NOASSERTION, LicenseRef-* without an approved exception. The
unknown is treated as forbidden, not as pending: «pending» means it gets
merged and nobody comes back.
- ❌ Strong copyleft (GPL/AGPL) in a distributed artifact or in a network service, without a
registered exception.
- ❌ Licence change of an existing dependency between two versions — it is the event
of §6.2 and must alert even if the new licence is also allowed.
- ❌ Absence of an artifact SBOM in a release build.
False positives and negatives, honestly: manifest-based detection has a structural false
negative (§3.6) and text-based detection has abundant false positives (a
sample LICENSE inside a test directory sets off alerts). Every suppression of a
finding is recorded with a reason and expires — the same model as a VEX in
vulnerability-management-standards. A suppression with no date is a permanent exception
in disguise.
5. Policy, inventory and obligations
5.1 The three lists
The policy has exactly three categories, and the list is published in the repo, not in a
wiki nobody reads:
| Category |
Typical content |
Rule |
| Allowed |
MIT, BSD-2/3-Clause, ISC, Apache-2.0, Apache-2.0 WITH LLVM-exception, Unlicense, CC0-1.0, Zlib |
Self-approved. The gate does not ask |
| With review |
MPL-2.0, EPL-2.0, LGPL-, CDDL-1.0, GPL- with -or-later, duals with ee/, any LicenseRef-* |
Approved per dependency and per use case (distributed / internal / network), with an owner and a date. The approval is not transitive to another project |
| Forbidden |
AGPL-* in a distributed product or SaaS, SSPL, ELv2, BUSL, RSALv2, PolyForm, FSL, FCL, MSCL, CC--NC-, «no licence» |
Breaks the build. Lifting it requires a formal exception (§5.3) |
These lists are a starting point and depend on your business model: if you do not distribute
software and do not offer a network service, AGPL may be perfectly acceptable; if you sell a
product installed at the customer's premises, LGPL with static linking is already a problem.
Explicit prohibition: do not copy these three lists without declaring the distribution model they
apply to. A licence policy without a declared distribution model cannot be
applied, only obeyed blindly.
5.2 Inventory
It is maintained per deployable artifact, not per repository, and is derived from the SBOM: name,
version, verified SPDX expression (not the manifest's), source of the datum (manifest /
scanned text / manual review), verification date, and if it is DOSP, the conversion
date (§3.1). It is regenerated on every release; a hand-maintained inventory is a
false inventory within three months.
5.3 Exceptions
Name of the dependency, version, licence, reason, alternative evaluated and why it was
discarded, scope (specific project and distribution mode), approver, and mandatory
expiry date. Without an expiry it is not an exception, it is a policy change through the
back door. The formal acceptance of residual risk is recorded where
grc-compliance-standards dictates; here lives the technical control that makes it enforceable.
5.4 Attribution: the obligation almost nobody meets
Almost every permissive licence requires preserving the copyright notice and the text of
the licence when redistributing. It is the most breached obligation in the industry, precisely because
it is the easiest: nobody audits a THIRD-PARTY-NOTICES until a big customer audits it.
- It is generated in the build from the SBOM (ORT does it; so do the native generators) and is
versioned with the artifact.
- It is included in the artifact itself when distributed: in the image, in the package, in
the application's «About». A file in the repository does not travel with the binary.
- Apache-2.0: the dependency's
NOTICE is propagated, the licence text alone is not enough.
- Copyleft: you must additionally offer the corresponding source code — with a valid offer
and a channel that really exists. A written offer pointing at a switched-off server is
a breach, not a formality.
5.5 SBOM: generating it is not using it
Generating an SBOM and not consuming it is a ticked box, not a control. The SBOM is useful if:
(a) the licence gate reads it, (b) CVE triage reads it
(vulnerability-management-standards), (c) attribution is generated from it, and (d) you can
answer «which deployed versions contain component X?» in minutes. If you do not
consume it in at least (a) and (b), do not generate it yet: fix that first.
Regulatory obligation — Cyber Resilience Act (EU), Regulation (EU) 2024/2847. Verified
dates (§8): entry into force 10-Dec-2024; 11-Jun-2026 application of Chapter IV
(notification of conformity assessment bodies); 11-Sep-2026 application of the
reporting obligations —actively exploited vulnerabilities and severe incidents,
with early warning within 24 h and notification within 72 h, through ENISA's single
platform (art. 16)—; 11-Dec-2027 full application, including essential requirements,
conformity assessment, technical documentation, CE marking and SBOM. The SBOM requirement
of Annex I, Part II, point 1 requires identifying and documenting the components «in a commonly
used and machine-readable format», covering at the very least the top-level dependencies.
Penalties of up to €15M or 2.5 % of annual worldwide turnover, whichever is higher.
Consequence the date hides: even though the SBOM is enforceable in Dec 2027, from Sep 2026
you have 24 hours to report an exploited vulnerability, and in 24 hours you cannot investigate by
hand which components a product shipped three years ago contains. The SBOM is an operational
prerequisite of the 2026 obligation, not of the 2027 one.
USA: the SBOM requirement in federal public procurement comes from EO 14028 (2021) and its
implementation (NIST guidance, NTIA minimum elements, OMB memoranda on vendor
attestation). Gap: the exact status of these orders and memoranda as of Aug 2026 has not been
verified in this drafting — see §8. No US date is cited here.
Scope rule, and it is the boundary with the vulnerability skill: the CRA is above all
a security obligation; its risk management, notification and triage belong to
vulnerability-management-standards and grc-compliance-standards. What stays here is the SBOM as an
artifact: which format, when it is generated, from what it is generated and which licence fields it carries.
6. Life cycle: relicensing, contributions and AI artifacts
6.1 Contributing outwards
- DCO (
Signed-off-by:, verified in CI): the contributor certifies that they have the right to
contribute. No transfer of rights, no legal friction. Default.
- CLA: assigns or licenses rights to the project. It has only one real motive — being able to relicense
later or sell proprietary exceptions. It is legitimate, but requiring a CLA and presenting yourself
as community-driven without explaining why is where the distrust begins. If you ask for it, say so.
- Risk signal for the consumer: a project with a full-assignment CLA can
relicense tomorrow without asking anyone's permission. That is not a reason to discard it; it is a reason
to put it on the radar of §6.2. Almost every relicensing in §3.6 happened in projects
with a CLA and a single corporate owner. **The combination «single corporate owner
- assignment CLA» is the best available predictor of a future relicensing.**
- Employee and contractor work: ownership depends on the contract and the
jurisdiction, and contributing to an external project with a personal account from the
company laptop does not change it by itself. That an internal contribution policy exists is a
requirement; its drafting is a matter for legal counsel (§1).
6.2 When a dependency relicenses under your feet
Four steps, in order, and none of them is optional:
- Detection. The full-graph gate must compare the licence against the one recorded in
the inventory and alert on any change, even if the new one is also allowed.
Detecting this by reading Hacker News is the industry's default state and is not a process.
- Impact assessment. Three questions, and only three: do we distribute the artifact that
contains it? Do we offer it over a network? Do we exceed the threshold of the free grant
—revenue, employees, number of repos, number of servers— today and in 18 months? The
thresholds of §3.6 ($5M/50 employees for Directus, ~$25M for Akka) are the part that grows
with you: a dependency that is free today may stop being free without changing version, just
because the company grew. Add the threshold to the inventory alongside the version.
- Decide between four exits (and not the fifth, which is not deciding):
- Pay for the commercial licence. It is a legitimate option and often the cheapest. Migrating
on principle comes out dearer than paying for a tool that works.
- Migrate to the community fork. It is a real and proven option, not theoretical:
OpenTofu (Terraform→BUSL; in the CNCF since Apr 2025, same provider binaries,
full compatibility, and already with its own divergent functionality such as native state
encryption), OpenBao (Vault→BUSL; MPL-2.0, API compatible, adopted by Nvidia),
Apache Pekko (Akka→BSL; graduated at the ASF, but with deliberate incompatibility of
packages, configuration and ports — it is not a change of Maven coordinate), Valkey
(Redis→RSALv2/SSPL, under the Linux Foundation), OpenSearch (Elasticsearch→SSPL/ELv2,
transferred to the Linux Foundation), Railroader (Brakeman). The best predictor that
a fork survives is that it has a neutral home (ASF, LF, CNCF); those th
…(truncated)
1---2name: opensource-licensing-standards3description: Use when a dependency's license is a hard engineering constraint — checking a LICENSE, COPYING, NOTICE or LICENSES/ file before adding a package, SPDX identifiers and expressions (MIT, BSD-3-Clause, Apache-2.0, Apache-2.0 WITH LLVM-exception, MPL-2.0, LGPL-3.0-only, GPL-2.0-only, GPL-3.0-or-later, AGPL-3.0-only, EPL-2.0, CDDL-1.0, CC-BY-NC-SA-4.0), source-available and fair-source terms (BUSL-1.1, Elastic License 2.0, SSPL-1.0, RSALv2, PolyForm Shield/Noncommercial, Functional Source License FSL, Fair Core License FCL, Monospace Sustainable Core License), a dependency that relicensed under you and the community fork that followed (Pekko, OpenTofu, OpenBao, Valkey, OpenSearch, Railroader), static versus dynamic linking and whether a SaaS distributes, AGPL network copyleft, Apache-2.0 patent grant and its GPL-2.0 incompatibility, dual licensing with a proprietary ee/ directory, an allowed/review/forbidden license policy and the CI gate that enforces it (dependency-review-action allow-licenses, cargo-deny deny.toml, go-licenses, pip-licenses, liccheck, license-checker, ORT, ScanCode Toolkit, FOSSology, Syft, Trivy), REUSE compliance and reuse lint, generating and consuming an SBOM in SPDX or CycloneDX, EU Cyber Resilience Act SBOM duties, a THIRD-PARTY-NOTICES attribution file, CLA versus DCO and Signed-off-by, or the license of a model, dataset or generated artifact.4metadata:5 source: https://skillmd.com/skills/serialexperimentslainnnn/opensource-licensing-standards6---78# Open source licensing and compliance standards910Criteria verified as of **August 2026**. Re-verify on the web before committing to anything (§8).1112## 1. Scope and triggers1314**The licence is an engineering constraint, and it is verified at the moment the dependency is15added — not when the customer turns up asking.** An incompatible licence discovered in a16two-year-old `git log` is not a legal finding: it is an **architectural debt** that is already17in production, in the customer's installer and in the image you signed. Checking it costs18seconds in the PR; discovering it in *due diligence* costs a redesign.1920Operational corollary, and it is the entire thesis of this document: **the gate goes in the PR21that adds the dependency**. A quarterly scan of the whole tree produces reports; a gate in the PR22produces decisions. If you can only have one, have the gate.2324**Scope notice — this is NOT legal advice.** What is here is engineering and compliance25criteria: what gets verified, what breaks the build, what gets recorded and who approves an26exception. **The interpretation of a clause, the assessment of contractual risk and any27decision with legal exposure are referred to qualified legal counsel** — notably: strong28copyleft entanglement in a distributed product, obligations under a vendor contract,29non-compete clauses of *source-available* licences, ownership of an employee's or contractor's30work, and any response to a compliance claim. This document says **when you have to ask a31lawyer**; it does not answer for one.3233Covers: what is and is not open source (the OSI's OSD and the *source-available* /34*fair-source* debate); licence families and what they actually require; compatibility and the35direction of combinations; the distinctions that cause almost every mistake (static vs. dynamic36linking, distribution vs. internal use, container vs. binary, SaaS); **SPDX** as the canonical37identifier; **SBOM** and its real regulatory obligation; the **process**: policy, CI gate,38scanning, inventory, exceptions and attribution; what to do when a dependency39**relicenses**; contributing outwards (CLA vs. DCO); and the licence of models, datasets and40content.4142Triggers: `LICENSE`, `LICENSE.md`, `LICENSE.txt`, `COPYING`, `NOTICE`, `LICENSES/`,43`REUSE.toml`, `.reuse/dep5`, `THIRD-PARTY-NOTICES`, `deny.toml`, `.licenserc`,44`dependency-review-action`, `allow-licenses`, `deny-licenses`, `cargo deny check licenses`,45`go-licenses`, `pip-licenses`, `liccheck`, `license-checker`, `reuse lint`, `scancode`,46`FOSSology`, ORT (`.ort.yml`, `evaluator.rules.kts`); SPDX identifiers (`MIT`,47`Apache-2.0`, `MPL-2.0`, `GPL-3.0-or-later`, `AGPL-3.0-only`, `LGPL-3.0-only`, `EPL-2.0`,48`CDDL-1.0`, `BSD-3-Clause`, `WITH LLVM-exception`, `LicenseRef-*`); SPDX expressions49(`AND`, `OR`, `WITH`); *source-available* (`BUSL-1.1`, ELv2, SSPL, RSALv2, PolyForm, FSL, FCL,50MSCL); `SPDX-License-Identifier:` in a file header; SBOM (`bom.json`, `*.spdx.json`,51CycloneDX, `syft`, `trivy sbom`); CRA; CLA, DCO, `Signed-off-by:`; relicensing, forking.5253### This skill is the CROSS-CUTTING OWNER of the subject5455**Every skill in the catalogue verifies the licence of the tools it pins** — and several have56done so and found surprises (§3.6). That is right and must continue. But **the licence policy,57the gate that enforces it and the exception process live HERE, and only here**. A language58skill decides *which linter to use*; it does **not** decide whether AGPL is acceptable in the59product. If another catalogue skill contradicts the policy of §5.1, **this one wins**.6061> **Precedent that justifies the procedure in §6, verified in this series**: in **YottaDB** the62> file called `LICENSE` **does not contain the licence** —it is explanatory copyright text—; the63> real licence (**AGPLv3**) is in `COPYING`. And **GnuCOBOL** is GPLv3 in the compiler but64> **LGPLv3 in the runtime**, with the added trap that its ISAM backend via Berkeley DB drags in65> Oracle conditions. Operational consequence: **it is not enough to read the file called66> `LICENSE`; you have to read the one that contains the licence**, and check whether compiler and67> runtime go separately.68>69> **Variants of the same failure, all confirmed in the catalogue** — any mechanical check70> that assumes `raw.../main/LICENSE` produces **false negatives**: file with **another name**71> (`COPYING` in YottaDB), **another extension** (`LICENSE.txt` in NetBox, `LICENSE.md` in Traefik),72> **another capitalisation** (`License.txt` in Lucee, `license.txt` in BoxLang) and **another default73> branch** (`master` in Angie, `7.0` in Lucee, `development` in BoxLang). And an extra warning:74> **GitHub's automatic licence classification gets it wrong** — it marks BoxLang as75> `NOASSERTION` because it carries a commercial preamble in front of a perfectly valid76> Apache-2.0 text. **The API is not a substitute for reading the file.**7778**Not applicable**: see `vulnerability-management-standards` (**thin and reciprocal boundary: the same79SBOM serves both and that is why they get confused**. The SBOM is generated once and consumed80twice: *for CVEs* —triage, EPSS/KEV, VEX, patching SLA— **theirs**; *for licence81obligations* —what I may combine, what I must publish, what I must attribute— **belongs here**.82Rule: if the question is "can this compromise me?", it is theirs; if it is "does this oblige me to83anything?", it belongs here), `cicd-standards` (**the pipeline runs the gate**: the runner, the job,84the cache, the OIDC and the artifact signature are theirs; **the threshold, the allowlist and what85breaks the build belong here**), `grc-compliance-standards` (**the corporate regulatory framework, the86risk register, the formal acceptance and the audit evidence are theirs**; here the technical control87that feeds them and the licence inventory), `secrets-management-standards` (a commercial licence88key —Directus, gitleaks-action— **is a secret and is managed there**; that you need one is a89licence fact and belongs here), `appsec-standards` (vulnerability classes90and SAST/DAST selection; **that Brakeman is not free belongs here**), `ai-governance-standards`91(**the governance of AI use —system inventory, AI Act, impact assessment— is92theirs; the licence of the artifact —weights, dataset, provider terms of use— belongs here**),93`ai-agent-workflow-standards` (**already written**: the licence and authorship of code generated by an94agent **is declared there as an UNRESOLVED question**. That is respected: this skill **does not invent95an answer**, it only fixes the procedure of §6.4 —traceability and provenance96verification— which is valid regardless of how it gets resolved), `git-workflow-standards`97(**the repository's licence file, the `Signed-off-by` and the commit signature are98theirs**; which licence to put and why to require DCO instead of CLA belongs here), and the language99skills —`python-standards`, `go-standards`, `rust-standards`, `typescript-standards`,100`java`/`jvm-spring-standards`, etc.— (**the specific package manager, its lock file101and its ecosystem's scanning command are theirs**; the policy that command applies belongs102here). With `green-it-standards`: **the licence of carbon measurement tools is103governed by this skill**. **Here only the *free* licence**: the **proprietary commercial licence** and104the **vendor audit** —named user, indirect access, annual measurement and declaration—105belong to `erp-sap-standards` and `crm-salesforce-standards`.106107## 2. Default decisions108109> Verify the latest version on the web before pinning it in a real project (§8).110111| Area | Default | Reason / justifiable alternative |112|---|---|---|113| Licence of what you publish (library) | **Apache-2.0** | It is the permissive one with an **explicit patent grant** (§3.2). MIT/BSD-3 only if the ecosystem imposes it (npm, Go). In Rust, the idiom is `Apache-2.0 OR MIT` — the `OR` exists precisely to provide a way out of the GPL-2.0 incompatibility |114| Licence of an internal, non-distributed application | **Proprietary / no public licence** | Not publishing is not an oversight; publishing without deciding to is. A repo with no `LICENSE` **is not open source**: without an express grant, all rights are reserved by default |115| Identifier | **SPDX expression** in `LICENSE`, in the package metadata and in the header (`SPDX-License-Identifier:`) | The only format a gate can parse. Free prose = manual review |116| Licence list | **SPDX License List** — verify the current version (§8) | It is the gate's vocabulary. Anything unlisted goes as `LicenseRef-...` and **enters manual review by definition** |117| SPDX specification | **3.0.1** (Dec 2024) as the published version; 3.1 in *release candidate* since Jan 2026 | Do not confuse the **specification** version (3.0.1) with the **list** version (3.x independent, at 3.28.0 as of Feb 2026). Verify both separately (§8) |118| SBOM format | **CycloneDX** for internal consumption; **SPDX** when the customer or regulator requires it | Verify the version your consumer accepts before generating: some consumers reject the latest minor. This version criterion is coordinated with `vulnerability-management-standards` |119| SBOM generation | **Syft** (or `trivy sbom`) in the build pipeline, over the **artifact**, not over the repo | The repo's SBOM does not describe what you deploy. Verify the tool's licence and status (§8) |120| Licence detection (deep) | **ScanCode Toolkit** (Apache-2.0) | Scans the actual text of files, not the manifest. It is the only way to detect the cases in §3.6 |121| *Clearance* and review workflow | **FOSSology** (GPL-2.0) if there is a formal audit obligation | Verify the tool's licence before integrating it into a product: FOSSology is strong copyleft, which **is irrelevant for using it and relevant if you embed it** |122| CI orchestration | **ORT (OSS Review Toolkit)**, Apache-2.0 | Runs ScanCode + evaluates against your policy + generates attribution. It is the only one on the list that does all three. Cost: it is a project in itself |123| PR gate (GitHub) | **`dependency-review-action` with `allow-licenses`** — **never** `deny-licenses` | `deny-licenses` is **deprecated** and slated for removal in the next major. And the underlying argument is correct: a list of forbidden ones will always forget one (the classic: you forbid `GPL-2.0` and `CC-BY-SA-4.0` comes in). **Allowlist or no gate** |124| Per-ecosystem gate | **The native tool**: `cargo-deny` (Rust), `go-licenses` (Go), `pip-licenses`/`liccheck` (Python), `license-checker` (npm), `dependency-license-report` (JVM) | `dependency-review-action` only sees the dependencies **that change in the PR**; the native gate sees the whole graph. **You need both**, and both as *required status checks* |125| Authorship marking in the repo | **REUSE** (`LICENSES/`, `SPDX-License-Identifier` headers, `reuse lint` in CI) | Verify the current version of the specification (§8; there was 3.3 from Nov 2024 with signs of a later 3.4 — **declare the discrepancy**, see §8). Practical warning: GitHub identifies the licence with `licensee`, which does **not** understand REUSE — leave a `LICENSE` at the root as well as the directory |126| Attribution when distributing | **`THIRD-PARTY-NOTICES.txt` generated in the build**, versioned alongside the artifact | Generated, not hand-written: a manual file is out of date on day 2. See §5.4 |127| Incoming contributions | **DCO** (`Signed-off-by:`) | Less friction and sufficient for most projects. **CLA** only if you need to relicense or sell exceptions — and then say out loud that that is the reason (§6.1) |128129## 3. What open source is, what it is not, and what each family requires130131### 3.1 The definition and the edge132133The **Open Source Definition** (OSI) opens, **verbatim**:134135> «Open source doesn't just mean access to the source code. The distribution terms of136> open source software must comply with the following criteria:»137138and lists ten criteria, whose titles are, **verbatim**: *Free Redistribution*; *Source139Code*; *Derived Works*; *Integrity of The Author's Source Code*; *No Discrimination Against140Persons or Groups*; *No Discrimination Against Fields of Endeavor*; *Distribution of License*;141*License Must Not Be Specific to a Product*; *License Must Not Restrict Other Software*;142*License Must Be Technology-Neutral*. The document identifies itself as **«Version 1.9, last143modified, 2007-03-22»**.144145**Hard rule**: criterion 6 (*No Discrimination Against Fields of Endeavor*) is the one that146rules out almost everything *source-available*. A clause saying «you may not offer this as a147competing service» or «not for commercial use» **discriminates against a field of endeavour** and148therefore **is not open source**, however much the repository sits on GitHub and says «open» on the front page.149150Status as of Aug 2026 of the licences that cause the most confusion — **none approved by the OSI**:151152| Licence | What it is | Note |153|---|---|---|154| **SSPL-1.0** | *source-available*, copyleft extended to the service *stack* | MongoDB withdrew it from the OSI submission in 2019; in Jan 2021 the OSI declared that it **does not meet the OSD** because it discriminates against fields of endeavour, and called it *«fauxpen» source* |155| **Elastic License 2.0 (ELv2)** | *source-available*, forbids offering it as a managed service | Elastic itself describes it as **not OSI-approved** |156| **BUSL-1.1 / BSL** | non-compete + **deferred conversion to open source** (4 years by default) | «BSL is not an OSI approved license» — statement by Elastic itself. The *Additional Use Grant* is **variable per project**: you have to read the one for the specific project, not «the BUSL» |157| **RSALv2** | Redis's *source-available* | — |158| **PolyForm Shield / Noncommercial / Perimeter** | *source-available* with an anti-competition or non-commercial clause | — |159| **FSL** (Functional Source License) | *fair source*: non-compete + conversion to Apache-2.0 or MIT **after 2 years** | Created by Sentry as a simplification of the BUSL, fixing its variables |160| **FCL** (Fair Core License) | variant of FSL «that includes license key support» (fair.io, verbatim) | Adds limitations derived from ELv2 |161| **MSCL** (Monospace Sustainable Core License) | derived from FCL, used by Directus v12 | See §3.6 |162163**Fair Source** is defined around three conditions: publicly readable code, use /164modification / redistribution with minimal restrictions, and **delayed open source publication165(DOSP)**. fair.io recognises, verbatim: **FSL** («A simple non-compete license with166eventual Open Source conversion after two years»), **FCL** («A variant of FSL that includes167license key support») and **BUSL/BSL** («A complex non-compete license with eventual Open Source168conversion after a certain amount of time, usually four years»). *Fair source* **is not open169source and does not claim to be**; the conflict is one of nomenclature, not of honesty.170171**Declared discrepancy**: the OSI itself is the source of the concept of *Delayed Open Source172Publication* that underpins the *fair source* designation, and at the same time members of its board173publicly hold that these licences **are not open source** because their freedoms do not174reach everyone and non-compete is «legally fuzzy». **Both things are true at175once**: the OSI recognises the *mechanism* (DOSP) and rejects the *label*. Do not cite one without the other.176177**Operational consequence of deferred conversion** — and almost nobody exploits this: in a178licence with DOSP, **each specific version has its own conversion date**. Akka moved to179BSL in 2022 and its versions revert to Apache-2.0 **36 months after their publication**;180Akka 2.7.0 has already reverted. Rule: **a licence with DOSP is not evaluated as a licence, it is evaluated181as a calendar** — record in the inventory the version, its publication date and its182conversion date, because the answer changes over time without anyone touching anything.183184### 3.2 Families and what they actually require185186**Permissive — MIT, BSD-2/3-Clause, ISC, Apache-2.0.** They require **preserving the copyright187notice and the licence** when redistributing. That is already a real obligation and it is the most188breached one (§5.4). **The technical reason to prefer Apache-2.0 over MIT is not copyleft: it is the189express patent grant** and its termination clause —if you sue a user of the software over190patents, you lose the patent licence—. MIT and BSD are silent on191patents, and silence is not a grant. Apache-2.0 additionally adds the `NOTICE` file192obligation: if the project ships one, **you propagate it**.193194**Weak copyleft.**195- **LGPL (2.1 / 3.0)**: the copyleft reaches the library, not your application, **on condition196 that the end user can replace the library with another version**. With **dynamic linking**197 that is trivial; with **static linking** it requires delivering objects or sources that allow198 relinking. LGPL-3.0 additionally adds the anti-*tivoization* clause inherited from GPL-3.0.199 **Real precedent from the catalogue: Pa11y is LGPL-3.0**, not MIT.200- **MPL-2.0**: the copyleft is **per file, not per project**. You modify a covered `.js` →201 that file remains MPL and you publish that modified file. Your new code in new files202 **is not contaminated**. This makes it suitable for combining with proprietary code, and it is the203 reason so many development tools choose it. **Real precedents:204 axe-core, StyLua, selene, Lightning CSS and `data.table` are MPL-2.0**; OpenBao too.205- **EPL-2.0**: copyleft at «module» scope, with *source availability* obligations and its own206 patent clause. Fine point: **EPL-2.0 allows designating the GPL as a secondary licence**207 — if the project has done so, the compatibility answer changes. **Read it in208 the file, do not assume it.**209210**Strong copyleft.**211- **GPL-2.0 vs. GPL-3.0**: they are not the same decision. GPL-3.0 adds anti-*tivoization*212 (an obligation to deliver installation information on consumer hardware), an express213 patent grant and compatibility with Apache-2.0. **`GPL-2.0-only` and `GPL-2.0-or-later` are214 different licences and the gate must distinguish them**: `-or-later` lets you move up to 3.0 and215 resolve incompatibilities; `-only` does not. **Real precedent: perltidy is GPL-2.0.**216- **AGPL-3.0 — the «network use» trigger, and it is the one that kills a SaaS.** GPL requires delivering217 sources **when distributing**; AGPL additionally requires offering the *Corresponding Source* **to218 users who interact with the program over a network**, even if you never distribute a219 binary. **This turns «we do not distribute, therefore it does not apply to us» —the correct reasoning220 for GPL in a SaaS— into a falsehood.** The scope is the modified program and its *Corresponding221 Source*, not your whole *stack* (that is SSPL, and that is why SSPL is not open source). **Real222 precedents: k6, Pyroscope, Slither, Echidna and Medusa are AGPL-3.0**; and Elasticsearch (2024) and223 Redis 8 (2025) returned to the OSD **via AGPL**, precisely because it deters resale224 as a service without leaving the definition.225- **CDDL-1.0 — it turns up where nobody expects it.** Per-file copyleft (like MPL-1.1, from which226 it descends) and **considered incompatible with the GPL by the FSF**, among other things because of its227 jurisdiction clauses. It is the reason for the eternal ZFS-in-the-Linux-kernel problem.228 **Real precedent from the catalogue: FlameGraph is CDDL**, and it shows up in any229 profiling workflow without anyone looking at it.230231**Exceptions (`WITH`).** An SPDX exception **changes the result**: `Apache-2.0 WITH232LLVM-exception` (Wasmtime, and the whole LLVM ecosystem) exists precisely to avoid233attribution obligations in linked binaries and to ease combination. Treating234`Apache-2.0 WITH LLVM-exception` as plain `Apache-2.0` is an analysis error, not a235nuance. **The gate must understand the `WITH` operator**; if your tool collapses it, you have a236false result and you do not know it.237238### 3.3 Compatibility: it is directional, not symmetric239240**The right question is never «are A and B compatible?», but «under which licence does the241combined work end up, and can I accept it?».** Compatibility has a direction of travel:242243- **Apache-2.0 → GPL-3.0**: they combine, and **the result is GPL-3.0**. Not the other way round: the244 GPL-3.0 code cannot go into an Apache project.245- **Apache-2.0 ↔ GPL-2.0-only**: **incompatible**. The FSF holds that all versions of246 the Apache License are incompatible with GPL v1 and v2, because of the patent and247 indemnity clauses. This is the most common and most silenced conflict in the real ecosystem, and the248 reason Rust is published as `Apache-2.0 OR MIT` (you pick MIT and the problem disappears)249 and why LLVM drafted its exception.250- **MPL-2.0 → GPL/LGPL**: MPL-2.0 was explicitly designed to be compatible (unlike251 MPL-1.1), unless the project has marked the file as *Incompatible With Secondary252 Licenses*. **That notice is in the file header: if you have not read it, you have not verified253 compatibility.**254- **CDDL ↔ GPL**: **incompatible** according to the FSF.255- **Permissive → proprietary**: always possible, with the attribution obligation intact.256257**Gate rule**: compatibility is not reasoned about in the PR, it is **decided once** in the258policy of §5.1 and the PR only checks membership of the list. Reasoning about compatibility in every259PR guarantees that one day it will be reasoned badly, in a hurry, on a Friday.260261### 3.4 The four distinctions that cause almost every mistake2622631. **Static vs. dynamic linking.** Determines whether LGPL requires you to allow relinking264 (§3.2). A Go binary is **always static**: in Go, «we link dynamically» is not an265 available option and that argument does not exist. A `FROM scratch` container with a266 static binary inside does not save you either.2672. **Distribution vs. internal use.** Classic copyleft (GPL, LGPL, MPL, EPL) triggers on268 **distributing**, not on using. GPL software used internally and never delivered to a third party269 **creates no obligation to publish**. That reasoning is correct **and AGPL voids it** (§3.2)270 — and so does a customer to whom you deliver a virtual machine, a `.deb`, an271 image or a device.2723. **Container vs. binary.** Delivering a container image **is distribution of everything273 inside it**: the base image, its system packages and its libraries, not just your274 application. Your source-code SBOM does not cover that. **That is why the SBOM is generated from the275 artifact** (§2). A base image with a GPL package you do not invoke **is still distribution276 of that package**.2774. **Does a SaaS distribute?** Under GPL/LGPL/MPL, the default operational answer is **no**: giving278 access to a service is not delivering copies. **Under AGPL, yes in practice**: the279 obligation towards network users is triggered. And there are two frequent leaks that break «we do not280 distribute»: **the code you send to the user's browser** (your JavaScript bundle *is*281 distributed, to each and every one) and **any agent, CLI or SDK the customer installs**.282 A backend that does not distribute with a frontend that does is the normal case, not the283 exception.284285### 3.5 SPDX and the file286287Canonical identifier, in three places and all three mandatory when you publish:288`LICENSE`/`LICENSES/` with the **full text**; the manifest's licence field with the289**SPDX expression**; and `SPDX-License-Identifier: <expr>` in the **header of every file**290(REUSE). Expressions: `AND` (you comply with both), `OR` (you pick one — **and you must record which one291you pick**, because `Apache-2.0 OR MIT` with no declared choice is a pending decision), `WITH`292(exception). Anything without a listed identifier goes as `LicenseRef-...` and **enters293manual review by definition** — a `LicenseRef` or a `NOASSERTION` is never self-approved.294295### 3.6 Why the manifest's `license` field LIES296297**This section is the core of the skill and its reason for existing.** During the construction of298this catalogue, **verifying the raw `LICENSE` file**, the following cases turned up —299all with third-party documentation claiming the opposite:300301| Case | What almost everyone says | What the file says |302|---|---|---|303| **Brakeman** | «MIT, it is the standard Rails scanner» | **Brakeman Public Use License**, proprietary to Synopsys. Code prior to 15-Jun-2018: MIT. Later: not free. **Scanning your own code is permitted; embedding it in a commercial product or service requires a commercial agreement.** Free fork of the pre-acquisition code: **Railroader** |304| **Directus** | «open source headless CMS» | Since **v12 (May 2026): Monospace Sustainable Core License**, derived from FCL. Free commercial use only via **Open Innovation Grant**, capped at **<$5M annual revenue and <50 employees**; conversion to **GPLv3 after 4 years**; mandatory **software key** (goodbye honour system). The SDKs remain MIT. **The package and the product do not share a licence** |305| **WebPageTest** | «open source web performance tool» | **PolyForm Shield**: *source-available* with an anti-competition clause |306| **FlameGraph** | «profiling script, MIT for sure» | **CDDL** — incompatible with GPL (§3.2) |307| **k6, Pyroscope** | «open source» (true) | **AGPL-3.0** — true and **relevant if you embed them in a service** |308| **Slither, Echidna, Medusa** | «Trail of Bits tools» | **AGPL-3.0** |309| **Pa11y** | «MIT like the rest of npm» | **LGPL-3.0** |310| **axe-core, StyLua, selene, Lightning CSS, `data.table`** | «MIT / permissive» | **MPL-2.0** (per-file copyleft) |311| **perltidy** | — | **GPL-2.0** |312| **Playwright** | — | **Apache-2.0** (not MIT) |313| **Extism** | — | **BSD-3-Clause** |314| **Wasmtime** | «Apache-2.0» | **Apache-2.0 WITH LLVM-exception** — the exception changes the analysis (§3.2) |315| **Tolgee, Strapi** | «open source» | **Dual, with a proprietary `ee/` directory in the same repository**. The repo has one licence; **parts of the repo have another** |316| **gitleaks** | «MIT» | The **scanner** is MIT and its author declared it *feature complete* (security patches only; successor: Betterleaks). The **GitHub action `gitleaks-action`** is **proprietary since v2.0.0** and **requires a licence key to scan an organisation's repositories** (free via form, with paid tiers by number of repos). **Two artifacts, two licences, same name** |317| **Infracost** | «Apache-2.0, free» | The **CLI** is Apache-2.0; **the hosted pricing API it depends on has a quota and a paid plan**. Free licence ≠ free operation |318| **Akka** | «Apache-2.0» | **BSL since 2.7.x** (2022), with a commercial threshold declared in the region of ~$25M revenue and **automatic reversion to Apache-2.0 after 36 months per version**. Fork: **Apache Pekko** (from 2.6.x, graduated at the ASF) |319| **Vault** | «open source» | **BUSL since 2023**. Fork: **OpenBao** (MPL-2.0, Linux Foundation) |320| **Trivy** | «Apache-2.0 as always» | **It changed licence** — verify the one for the artifact and version you use (§8) |321| **Elasticsearch** | «it went back to being open source» | **It added AGPL-3.0 (2024) alongside SSPL and ELv2 for the source code**. **Open gap: the licence of the binaries distributed by Elastic** — there are signs that the *releases* remain under the Elastic License even though the source is triple-licensed. **Not closed here: see §8** |322323**The five rules that follow, and they are the policy:**3243251. **The manifest's `license` field is a declaration by the packager, not a verified326 fact.** You read the `LICENSE` file **of the specific version you are going to use**.3272. **A repository may have more than one licence.** The `ee/`, `enterprise/` or328 `pro/` directory is the standard *open core* pattern; the root manifest **does not reflect it**.3293. **A project may have more than one artifact with different licences** (gitleaks vs.330 gitleaks-action; Directus core vs. SDK; Elasticsearch source vs. binary). **The unit of331 analysis is the artifact you install, not the project that publishes it.**3324. **The licence is tied to the version.** «X is MIT» is a meaningless statement without a version.3335. **Free licence ≠ free to operate** (Infracost) and **free licence ≠ maintained**334 (gitleaks). Verify all three things: licence, operating cost and project status.335336## 4. Gate quality: what gets checked and what breaks the build337338In increasing order of cost. The first three are mandatory; the fourth depends on whether you339distribute.3403411. **Precondition — lock file.** Without `uv.lock` / `package-lock.json` / `go.sum` /342 `Cargo.lock` / `poetry.lock` the graph is not deterministic and **any scan describes a343 resolution that will never happen again**. Without a lock there is no gate: there is theatre.3442. **PR gate (seconds).** `dependency-review-action` with `allow-licenses`. Fails if the345 **new** dependency brings a licence outside the allowlist. Practical note: `OTHER` is not346 a valid SPDX identifier and translates to `LicenseRef-clearlydefined-OTHER` — use it in347 that form in the list or you will get false greens.3483. **Full-graph gate (minutes, on every `main` build).** The ecosystem's native tool.349 **It breaks the build.** Specific warning: `cargo-deny` **removed** `deny`, `copyleft`,350 `allow-osi-fsf-free` and `unlicensed` — now **everything is denied except what is explicitly351 allowed**, which is exactly the right model; an old `deny.toml` with those fields352 **fails with an error**, it does not degrade silently. And check the scope: by default it excludes353 *dev-dependencies* and **includes *build-dependencies***, because those do influence the354 artifact.3554. **Deep text scan (nightly or per *release*).** ScanCode/ORT over the artifact.356 It is the only one that detects files with a header different from the project's, copied code and357 `ee/` directories. **It does not block the PR; it opens a ticket with an SLA.**3585. **`reuse lint`** if you publish: fails if any file lacks licence information.359360**What breaks the build (non-negotiable):**361- ❌ Licence outside the allowlist (§5.1).362- ❌ **Unknown** licence, `NOASSERTION`, `LicenseRef-*` without an approved exception. **The363 unknown is treated as forbidden**, not as pending: «pending» means it gets364 merged and nobody comes back.365- ❌ Strong copyleft (GPL/AGPL) in a distributed artifact or in a network service, without a366 registered exception.367- ❌ Licence change of an **existing** dependency between two versions — it is the event368 of §6.2 and must alert even if the new licence is also allowed.369- ❌ Absence of an artifact SBOM in a *release* build.370371**False positives and negatives, honestly**: manifest-based detection has a structural false372negative (§3.6) and text-based detection has abundant false positives (a373sample `LICENSE` inside a test directory sets off alerts). **Every suppression of a374finding is recorded with a reason and expires** — the same model as a VEX in375`vulnerability-management-standards`. A suppression with no date is a permanent exception376in disguise.377378## 5. Policy, inventory and obligations379380### 5.1 The three lists381382The policy has **exactly three categories**, and the list is published in the repo, not in a383wiki nobody reads:384385| Category | Typical content | Rule |386|---|---|---|387| **Allowed** | MIT, BSD-2/3-Clause, ISC, Apache-2.0, Apache-2.0 WITH LLVM-exception, Unlicense, CC0-1.0, Zlib | Self-approved. The gate does not ask |388| **With review** | MPL-2.0, EPL-2.0, LGPL-*, CDDL-1.0, GPL-* with `-or-later`, duals with `ee/`, any `LicenseRef-*` | Approved **per dependency and per use case** (distributed / internal / network), with an owner and a date. The approval **is not transitive to another project** |389| **Forbidden** | AGPL-* in a distributed product or SaaS, SSPL, ELv2, BUSL, RSALv2, PolyForm, FSL, FCL, MSCL, CC-*-NC-*, «no licence» | Breaks the build. Lifting it requires a formal exception (§5.3) |390391These lists **are a starting point and depend on your business model**: if you do not distribute392software and do not offer a network service, AGPL may be perfectly acceptable; if you sell a393product installed at the customer's premises, LGPL with static linking is already a problem.394**Explicit prohibition: do not copy these three lists without declaring the distribution model they395apply to.** A licence policy without a declared distribution model cannot be396applied, only obeyed blindly.397398### 5.2 Inventory399400It is maintained **per deployable artifact**, not per repository, and is derived from the SBOM: name,401version, **verified** SPDX expression (not the manifest's), source of the datum (manifest /402scanned text / manual review), verification date, and **if it is DOSP, the conversion403date** (§3.1). It is regenerated on every *release*; a hand-maintained inventory is a404false inventory within three months.405406### 5.3 Exceptions407408Name of the dependency, **version**, licence, reason, **alternative evaluated and why it was409discarded**, scope (specific project and distribution mode), approver, and **mandatory410expiry date**. Without an expiry it is not an exception, it is a policy change through the411back door. The **formal acceptance of residual risk** is recorded where412`grc-compliance-standards` dictates; here lives the technical control that makes it enforceable.413414### 5.4 Attribution: the obligation almost nobody meets415416**Almost every permissive licence requires preserving the copyright notice and the text of417the licence when redistributing.** It is the most breached obligation in the industry, precisely because418it is the easiest: nobody audits a `THIRD-PARTY-NOTICES` until a big customer audits it.419420- It is **generated in the build** from the SBOM (ORT does it; so do the native generators) and is421 versioned with the artifact.422- It is included **in the artifact itself** when distributed: in the image, in the package, in423 the application's «About». A file in the repository does not travel with the binary.424- Apache-2.0: **the dependency's `NOTICE` is propagated**, the licence text alone is not enough.425- Copyleft: you must additionally offer the **corresponding source code** — with a valid offer426 and a channel that really exists. A written offer pointing at a switched-off server is427 a breach, not a formality.428429### 5.5 SBOM: generating it is not using it430431**Generating an SBOM and not consuming it is a ticked box, not a control.** The SBOM is useful if:432(a) the licence gate reads it, (b) CVE triage reads it433(`vulnerability-management-standards`), (c) attribution is generated from it, and (d) you can434answer «which deployed versions contain component X?» in minutes. If you do not435consume it in at least (a) and (b), do not generate it yet: fix that first.436437**Regulatory obligation — Cyber Resilience Act (EU), Regulation (EU) 2024/2847.** Verified438dates (§8): entry into force **10-Dec-2024**; **11-Jun-2026** application of Chapter IV439(notification of conformity assessment bodies); **11-Sep-2026** application of the440**reporting obligations** —actively exploited vulnerabilities and severe incidents,441with early warning within **24 h** and notification within **72 h**, through ENISA's single442platform (art. 16)—; **11-Dec-2027** **full** application, including essential requirements,443conformity assessment, technical documentation, CE marking and **SBOM**. The SBOM requirement444of Annex I, Part II, point 1 requires identifying and documenting the components «in a commonly445used and machine-readable format», **covering at the very least the top-level dependencies**.446Penalties of up to **€15M or 2.5 % of annual worldwide turnover**, whichever is higher.447448**Consequence the date hides**: even though the SBOM is enforceable in Dec 2027, **from Sep 2026449you have 24 hours to report an exploited vulnerability**, and in 24 hours you cannot investigate by450hand which components a product shipped three years ago contains. **The SBOM is an operational451prerequisite of the 2026 obligation, not of the 2027 one.**452453**USA**: the SBOM requirement in federal public procurement comes from EO 14028 (2021) and its454implementation (NIST guidance, NTIA *minimum elements*, OMB memoranda on vendor455attestation). **Gap: the exact status of these orders and memoranda as of Aug 2026 has not been456verified in this drafting — see §8. No US date is cited here.**457458**Scope rule, and it is the boundary with the vulnerability skill:** the CRA is above all459a **security** obligation; its risk management, notification and triage belong to460`vulnerability-management-standards` and `grc-compliance-standards`. What stays here is **the SBOM as an461artifact: which format, when it is generated, from what it is generated and which licence fields it carries**.462463## 6. Life cycle: relicensing, contributions and AI artifacts464465### 6.1 Contributing outwards466467- **DCO** (`Signed-off-by:`, verified in CI): the contributor certifies that they have the right to468 contribute. No transfer of rights, no legal friction. **Default.**469- **CLA**: assigns or licenses rights to the project. It has only one real motive — **being able to relicense470 later or sell proprietary exceptions**. It is legitimate, but **requiring a CLA and presenting yourself471 as community-driven without explaining why is where the distrust begins**. If you ask for it, say so.472- **Risk signal for the consumer**: a project with a full-assignment CLA **can473 relicense tomorrow without asking anyone's permission**. That is not a reason to discard it; it is a reason474 to put it on the radar of §6.2. Almost every relicensing in §3.6 happened in projects475 with a CLA and a single corporate owner. **The combination «single corporate owner476 + assignment CLA» is the best available predictor of a future relicensing.**477- **Employee and contractor work**: ownership depends on the contract and the478 jurisdiction, and contributing to an external project with a personal account from the479 company laptop does not change it by itself. **That an internal contribution policy exists is a480 requirement; its drafting is a matter for legal counsel** (§1).481482### 6.2 When a dependency relicenses under your feet483484Four steps, in order, and none of them is optional:4854861. **Detection.** The full-graph gate must **compare the licence against the one recorded in487 the inventory** and alert on any change, **even if the new one is also allowed**.488 Detecting this by reading Hacker News is the industry's default state and is not a process.4892. **Impact assessment.** Three questions, and only three: do we **distribute** the artifact that490 contains it? Do we offer it **over a network**? Do we exceed the **threshold** of the free grant491 —revenue, employees, number of repos, number of servers— today **and in 18 months**? The492 thresholds of §3.6 ($5M/50 employees for Directus, ~$25M for Akka) are the part that grows493 with you: **a dependency that is free today may stop being free without changing version, just494 because the company grew.** Add the threshold to the inventory alongside the version.4953. **Decide between four exits** (and **not** the fifth, which is not deciding):496 - **Pay for the commercial licence.** It is a legitimate option and often the cheapest. Migrating497 on principle comes out dearer than paying for a tool that works.498 - **Migrate to the community fork.** It is a **real and proven** option, not theoretical:499 **OpenTofu** (Terraform→BUSL; in the CNCF since Apr 2025, same provider binaries,500 full compatibility, and already with its own divergent functionality such as native state501 encryption), **OpenBao** (Vault→BUSL; MPL-2.0, API compatible, adopted by Nvidia),502 **Apache Pekko** (Akka→BSL; graduated at the ASF, **but with deliberate incompatibility of503 packages, configuration and ports — it is not a change of Maven coordinate**), **Valkey**504 (Redis→RSALv2/SSPL, under the Linux Foundation), **OpenSearch** (Elasticsearch→SSPL/ELv2,505 transferred to the Linux Foundation), **Railroader** (Brakeman). **The best predictor that506 a fork survives is that it has a neutral home** (ASF, LF, CNCF); those th507508…(truncated)