License inventory is documented
Why it matters
MIT, Apache-2.0, and BSD licenses all carry attribution requirements: you must preserve copyright notices and license texts when distributing the software. Without a license inventory, you cannot verify that you are meeting these obligations, and during any commercial transaction — acquisition, enterprise sales with contractual IP representations, or legal due diligence — the absence of a license inventory is a red flag that slows or blocks the deal. SSDF PW.4 treats third-party component tracking as a requirement, not a nice-to-have. A license inventory is also the prerequisite for any copyleft or conflict check to be meaningful: you cannot evaluate what you have not enumerated.
Severity rationale
Low because missing attribution documentation is a compliance gap rather than an active vulnerability, but it becomes a blocking issue during legal due diligence or enterprise sales.
Remediation
Generate and commit a license inventory file. Add a generation script to package.json so it stays current on every build:
npx license-checker --production --out LICENSES.txt --customPath '{name},{licenses},{repository}'
Or automate it in CI:
// package.json
"scripts": {
"licenses": "license-checker --production --out LICENSES.txt"
}
Commit the generated LICENSES.txt and add a CI step that fails if the file is out of date.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Dependency & Supply Chain Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- spdx · LicenseRef-scancode-unknown — License inventory documentation
- ssdf:800-218 · PW.4 — Reuse Existing, Well-Secured Software
- soc2:2017 · CC9.2 — Vendor and business partner management
Taxons
History
- 2026-04-18·v1.0.0·Initial import from dependency-supply-chain·automated
- 2026-07-06·v1.0.1·Add SOC 2 TSC mapping (CC9.2) from the verified compliance crosswalk register (docs/compliance/).·by soc2-mapping-enrichment-ship-2