Will It Vibe?SEE LICENSE IN references a missing file
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
package.json uses the SPDX "SEE LICENSE IN <file>" form to point at a custom license file, but no file with that name exists in the repository, so the actual license terms are unresolvable from the metadata alone.
Why it matters
The "SEE LICENSE IN <file>" form is a valid SPDX shorthand for a custom, non-standard license, but it only works if that file actually exists: when it does not, the license is completely unresolvable from the package's own metadata, which is worse than having no license field at all since it actively points somewhere empty.
How to fix it
Either add the referenced file with the actual custom license text, or if the filename was renamed or moved, update the "license" field to point at wherever the license text actually lives. If the project should really use a standard license instead of a custom one, replace both the field and the missing file with a standard SPDX identifier and matching LICENSE file.
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