No LICENSE file
Part of Documentation, UX & Accessibility, which counts for 15% of the overall score. When this check fires it deducts 2 points from that category, once per scan, no matter how many places it turns up.
What it detects
No LICENSE file was found, which leaves the legal terms of reuse undefined.
Why it matters
Without a LICENSE file, default copyright applies and nobody else can legally use, modify, or redistribute the code, even if the repo is public. Companies and serious contributors check for a license before touching a project, so its absence quietly turns people away. It also creates ambiguity for your own future use if collaborators contributed code.
How to fix it
Decide what you want: pick MIT or Apache-2.0 for permissive open source, a copyleft license like GPL-3.0 if you want derivatives to stay open, or keep the repo intentionally all-rights-reserved and say so in the README. Add the full license text as a LICENSE file at the repository root with the correct year and copyright holder, and set the "license" field in package.json (or pyproject.toml) to the matching SPDX identifier.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo