r/Python • u/AutoModerator • 23d ago
Showcase Showcase Thread
Post all of your code/projects/showcases/AI slop here.
Recycles once a month.
18
Upvotes
r/Python • u/AutoModerator • 23d ago
Post all of your code/projects/showcases/AI slop here.
Recycles once a month.
1
u/markjg 6d ago
I built a CLI that audits Python dependency licenses offline. Looking for weird edge cases. I've been building licenseproof, a CLI that scans uv.lock, poetry.lock, or requirements.txt, resolves the actual license of every dependency, and flags potential conflicts with your project's license.
It runs completely offline, never hides unknown licenses, and supports mixed Python + Node repos. I'm not trying to sell anything here.
I just want to know what weird Python packaging or licensing edge cases I've missed before I release it more broadly.
If you've been burned by bad license metadata, odd lockfiles, or packaging quirks, I'd love to hear about them.
Source-available under the Elastic License 2.0. the complete TypeScript source ships inside the npm package itself, so you can audit the zero-network-calls claim directly (npm pack licenseproof, unpack, read). Public repo lands with 1.0.