Will It Vibe?pyproject.toml has no license metadata
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 Python project (pyproject.toml at the repo root) declares no license through any of the three mechanisms tooling looks for: a PEP 621 "license" key, a PEP 639 "license-files" key, or a "License ::" trove classifier. PyPI and dependency scanners fall back to "unknown" for this package.
Why it matters
Without a "license" key, a "license-files" key, or a "License ::" classifier, PyPI and dependency scanners have no machine-readable answer for this package's terms, the same gap a missing license field causes for npm packages. Some corporate dependency-approval pipelines reject packages with no resolvable license outright.
How to fix it
Add a "license" field under the [project] table in pyproject.toml, either the short SPDX form (license = "MIT") or, for older tooling, a "License :: OSI Approved :: ..." classifier under [project.classifiers]. Make sure a matching LICENSE file exists at the repo root.
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