Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add uv license or similar to audit dependency licenses #8156

Open
autinerd opened this issue Oct 13, 2024 · 2 comments
Open

Add uv license or similar to audit dependency licenses #8156

autinerd opened this issue Oct 13, 2024 · 2 comments
Labels
wish Not on the immediate roadmap

Comments

@autinerd
Copy link

It would be cool to have a possibility to audit licenses of dependencies like pip-license does. (And including the new License-Expression in Metadata 2.4)

@charliermarsh charliermarsh added the wish Not on the immediate roadmap label Oct 14, 2024
@yayami3
Copy link

yayami3 commented Nov 29, 2024

I'm on board!

@ryanleary
Copy link

ryanleary commented Dec 13, 2024

@charliermarsh would an appropriate approach here to include license information in the uv.lock file? I am new to the uv codebase, but exploring the feasibility of adding this capability.

It seems that ideally given a set of dependencies pulled in from a Lockfile that we would then introspect the license and report back. I spent an ~hour exploring the Package and PackageMetadata data models. It seems like most of what is discovered by the resolver is ultimately serialized into uv.lock and I'm not sure that would be appropriate here.

I'm exploring the codepath of uv tree as that seems most conceptually similar. Given a list of Packages, what would the most sensible way be to access either (a) classifiers, and/or (b) pyproject toml license data?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wish Not on the immediate roadmap
Projects
None yet
Development

No branches or pull requests

4 participants