Will It Vibe?LICENSE file is empty or near-empty
Part of Dependencies & Hygiene, which counts for 10% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A root license-family file exists but holds fewer than 20 non-whitespace characters, so it cannot actually be a license grant: this is almost always a placeholder that was created but never filled in.
Why it matters
A LICENSE file with only a handful of characters is not a valid license grant to anyone reading it, so the repository is effectively unlicensed despite appearing to have addressed the question. This is easy to miss because the file's mere presence satisfies a quick visual check or an automated "does a LICENSE file exist" gate.
How to fix it
Fill in the actual license text that matches package.json's declared license, or your intended license if none is declared yet. Use the standard template text for that license (for example the standard MIT or Apache-2.0 boilerplate with the copyright year and holder filled in) rather than writing custom legal text.
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