licenseproof vs license-checker and FOSSA
These three tools get asked for in the same conversation, and they are not really the same kind of thing: one is a free npm utility, one is an enterprise platform, and licenseproof sits between them. This page says which is which, where each one is genuinely better, and where every claim came from.
Everything below about license-checker and FOSSA was read from public sources on 31 October 2026, with the source named inline. We did not run a benchmark against either one and this page does not claim to have. If something here is out of date or wrong, email us and it gets corrected — including if you maintain one of them.
The short version
- Use license-checker if you have an npm-only project, you want a free list of your dependency licenses, and a JSON or CSV dump is the artifact you need. It is genuinely free and genuinely open source. licenseproof's scanner is free too, but license-checker has nothing to sell you, which is worth something.
- Use FOSSA if you need a platform: “dozens of language ecosystems” (docs.fossa.com/docs/supported-languages, 31 Oct 2026), “automated license and vulnerability scanning” on their Business plan, and support running from “basic email support” to “enterprise-grade SLAs” (fossa.com/pricing, 31 Oct 2026). If your procurement process requires those, stop reading — we do not have them.
- Use licenseproof if you want the document, not a dashboard: a report you can hand to a customer's lawyer, generated offline on your own machine, for a one-time $29, covering npm and Python.
licenseproof vs license-checker
What license-checker is
- An npm CLI,
license-checker, licensed BSD-3-Clause — properly open source, unlike licenseproof. (npm registry metadata, 31 Oct 2026.) - Its README's own framing: “Ever needed to see all the license info for a module and its dependencies?” (github.com/davglass/license-checker.)
- Node and npm only. No Python support. (Its README documents installation and
node_modulesscanning, and mentions no other ecosystem.) - Output: a plain tree by default, plus
--jsonand--csv. (Its README.) - Latest published version is 25.0.1, published 10 January 2019. (
npm view license-checker version time, 31 Oct 2026.) That is the publishing record, and we make no claim about the project's maintenance beyond it.
Where licenseproof differs
- Python as well as npm. uv, poetry, requirements.txt and pyproject, alongside package-lock, pnpm and yarn. Mixed repos scan both at once. Conda and Pipenv are not supported.
- It produces the artifact, not just the list. An audit-ready HTML and PDF report with per-page provenance footers, a
THIRD_PARTY_NOTICESfile, and SBOMs — CycloneDX in the free tier, SPDX in the report tier. JSON and CSV are a starting point for a document; this is the document. Look at a real one. - Every answer says where it came from. licenseproof resolves each package through an ordered set of fallbacks and tags the result with its source and a confidence level, and when nothing resolves it reports
UNKNOWNrather than dropping the package. The full resolution order, per ecosystem. - It costs money. The scanner is free forever; the report tier is $29 one-time. license-checker costs nothing, ever. If the free list is all you need, that is the honest answer and you should take it.
licenseproof vs FOSSA
What FOSSA is
- A hosted software-composition-analysis platform. The free tier is “SaaS (multi-tenant cloud)”; enterprise plans mention “custom deployment options.” (fossa.com/pricing, 31 Oct 2026.)
- Free tier, with caps: 5 projects, 10 contributing developers, 1 release group, 5 dependency levels per scan, 1 quality check, 5 imported SBOMs. (fossa.com/pricing, 31 Oct 2026.)
- Its published price is $20 per project per month. (fossa.com/pricing, 31 Oct 2026.) That is the only cost figure we quote.
- It is scoped far wider than licensing alone — imported SBOMs and “Export SBOMs”, a “full suite of quality checks” and “multi-project reporting” are plan features, and their snippet-scanning add-on triages issues “based on your FOSSA policies.” It is a compliance programme you run, not a command you type. (fossa.com/pricing, 31 Oct 2026.)
Where licenseproof differs
- Nothing is uploaded. Zero network calls, zero telemetry, no account, verifiable in the source. Your dependency tree — which is a map of your architecture — never leaves your machine. For some teams that alone decides it.
- One-time, not per project per month. $29 once, perpetual. Past your update year the tool keeps working; you just stop pulling newer reference data. Nothing to renew, nothing to lose access to, no per-project meter.
- No caps to design around. No project limit, no developer count, no dependency-depth ceiling, because there is no server to meter.
- It does much less. No vulnerability or CVE data — FOSSA's Business plan includes “automated license and vulnerability scanning” (fossa.com/pricing, 31 Oct 2026). No policy engine, no dashboard, no roles, no org-wide history, no CI integration beyond an exit code. If you need any of that, licenseproof is not the tool and a platform is.
Where licenseproof is the wrong choice
Stated plainly, because a comparison page that only flatters its own product is worth nothing:
- Your stack is not npm or Python. Go, Java, Rust, Ruby, .NET and the rest are not scanned. FOSSA covers far more ecosystems — its docs say “dozens of language ecosystems”, Go, Java, Rust, Ruby and .NET among them (docs.fossa.com/docs/supported-languages, 31 Oct 2026); licenseproof covers two, properly.
- You need vulnerability management too. licenseproof has no CVE data and no plans stated here to add it.
- You need a dashboard and roles. There is no web UI. It is a CLI that writes files.
- You need a vendor. One independent developer, no SLA, no procurement paperwork. That is a legitimate blocker and we would rather you hit it here than after paying.
- You need a legal determination. licenseproof produces informational license categorization. It is not legal advice, and no automated tool is — FOSSA's output isn't either.
What we could not source
- What FOSSA costs beyond its published “$20 per project per month”. What a given team actually pays, and what any other plan runs, is quoted by their sales team and is not public — so no other number appears on this page.
- license-checker's maintenance status. All we source is its published version and the date it was published. We make no claim about intent or activity beyond that.
- Feature-by-feature parity. We did not run either tool against the same repository to compare resolution accuracy. If anyone publishes that comparison, we will link it even if we lose.