Some form of License check?

It occurs to me that uv is in a good position to some kind of license check as part of pre-commit. Especially with PEP 639 recently added.

Maybe it would depend on https://github.com/astral-sh/uv/issues/8156 / https://github.com/astral-sh/uv/pull/10292

In general I can imagine a few options I would be interested in, validate the name of the license, validate the text of the license up to some template (i.e. should match some standard text + copyright lines), only unknown licenses for specifically named dependencies, some distinction on PEP 639 license expressions vs. previous ad-hoc license text.

Not sure how much of an ask this is, understand if it's not a priority for Astral.

Start by reading this issue together with uv issue #8156 and pull request #10292 to understand the proposed dependency and metadata work. Compare the listed license-check options and identify which behavior, inputs, and completion criteria the project would accept; no implementation entry point or test file is named yet.

Written by the indexing model from the issue text.