LICENSE file exists and is stated in README
Why it matters
A missing LICENSE file means the code is, by default, all rights reserved — no one can legally use, fork, distribute, or embed it in their product. Enterprise legal teams explicitly block adoption of unlicensed code, and many package registries and distribution channels will flag or reject it. A mismatch between LICENSE (MIT) and package.json license field (ISC) also creates legal ambiguity that blocks commercial use until resolved.
Severity rationale
Low because unlicensed code blocks commercial adoption but has no runtime or security impact.
Remediation
Add a LICENSE file at the project root with the full text of your chosen license (MIT, Apache-2.0, GPL-3.0, etc.), reference it in the README, and set the matching license field in package.json. Example:
## License
MIT — see [LICENSE](./LICENSE) for details.
{ "license": "MIT" }
Verify the string in package.json matches the license file exactly, including spelling and version suffix.
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 Developer Documentation Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from developer-documentation·automated