OSS is everywhere, but not all licences are equal.
Earnie scans your code in real time, and matches the code itself, so a pasted function, a vendored library or a snippet a coding agent reproduced is found with its licence, checked against your policy and recorded.
Request a demoThe knowledge base behind every match
Open source URLs indexed
Matched by content, not by package name.
Lines of code fingerprinted
What a pasted snippet is compared against.
Sources
Including GitHub, npm, Maven Central, PyPI and Stack Overflow.
Smallest unit matched
Copied, vendored, modified or AI-generated code, with no manifest to read.
Source: the knowledge base’s live statistics. It grows every week.
From matched code to a shipped notice file
A licence programme has to cover what the code contains, not only what the team declared. Earnie handles it in five connected steps.
Match the code, not just the manifest
Earnie reads declared dependencies and fingerprints every file against the knowledge base, so copied and vendored code is found with the component it came from.
Illustrative example
Sort what you found by licence
Each component carries its detected licence. When a reviewer concludes a different one, Earnie keeps both.
Permissive
Weak copyleft
Strong copyleft
Unknown
Illustrative example
Check the match before you decide
Any finding opens beside the open source it matched, line by line. You confirm it, mark the code as your own, replace the component or reject the match.
your code: src/media/decode.c
62% snippet matchopen source: ffmpeg
Illustrative example
Apply one licence policy everywhere
Five licence templates run for coding agents over MCP, in developer self-checks and in pull request scans.
Also built in: Enforce license allowlist and Flag unknown licenses, both Require approval.
Ship the notice file with the release
The open-source distribution package freezes one scan and makes the SBOM, the notice file and a licence obligations report from it.
SPDX 2.3 Litelicence texts, copyright holders, obligationsper componentRun a licence through the policy
Pick the licence Earnie found, then how the code arrived.
Permissive
Weak copyleft
Strong copyleft
Unknown
Arrived as
Illustrative. The policies are Earnie’s five built-in licence templates with example values: AGPL-3.0-only on the banned list, and MIT, Apache-2.0 and BSD-3-Clause on the allowlist. You set your own.
A governance layer for your licence programme
Identify
Find open source in code and manifests, down to the snippet.
Review
Check each match side by side and record the decision.
Govern
Apply one licence policy wherever code enters.
Record
Export SBOMs and notice files, with the audit trail of every decision.
Which licences your organisation accepts, and how it meets their obligations, stays with your legal team or open source programme office. Earnie finds the licences, applies the policy you set and keeps the record. It isn’t legal advice.
Questions about licence compliance and Earnie
Can Earnie find open source that was copied in without a package manager?
Yes. Earnie identifies open source down to snippet level, so it finds code that was copied, vendored, modified or generated by AI, even when there is no manifest to read.
How is this different from a dependency licence check?
A dependency licence check covers the packages a change declares. Earnie reads those too, and also matches the files themselves, so a pasted function or a vendored library is found with its licence. The two work well together: keep the dependency gate, and add coverage for the code it can’t see.
Which licence policies are built in?
Five templates: Block banned licenses, Enforce license allowlist, Flag unknown licenses, Require approval for strong copyleft and Warn on weak copyleft. You set the licence lists, change the action and attach the policy to the projects it should govern.
Can I check a match myself?
Yes. Every finding opens into a side-by-side view of your code against the source it matched, with the match percentage. You then confirm the match, mark the file as your own code, replace the component or record that it isn’t a match, and Earnie keeps the decision.
What is the difference between an SBOM and a notice file?
An SBOM lists what’s present and names each component’s licence. A notice file, also called an attribution document, contains the text you’re obliged to distribute: licences, copyright holders, obligations and the full LICENSE and NOTICE text for each component. Earnie generates both from the same frozen scan.
Which formats does Earnie export?
SBOMs export in CycloneDX 1.7 and SPDX 2.3 Lite. The open-source distribution package bundles an SPDX SBOM, the notice file and a licence obligations report, and cites ISO/IEC 5230 (OpenChain) and Apache-2.0 section 4(d).
Does my code leave my environment?
No. Earnie runs on your own server and reads your code there. On SaaS, only fingerprints, one-way hashes of your code, go to the knowledge base we host. On-prem, nothing leaves your network.
Know what you’re shipping before legal asks.
See Earnie match licences on code like yours.
Request a demo