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

Shared license fixups #108

Open
jayvdb opened this issue Oct 5, 2024 · 1 comment
Open

Shared license fixups #108

jayvdb opened this issue Oct 5, 2024 · 1 comment

Comments

@jayvdb
Copy link

jayvdb commented Oct 5, 2024

I'm in the process of trying to switch over to using https://github.com/google/osv-scanner 's license checker, which uses deps.dev for this. I've raised a few bugs there, but I think this feature request belongs here.

https://github.com/jslicense/licensee.js includes a few license helpers in order to get the job done.

A dataset of corrections: https://github.com/jslicense/npm-license-corrections.json

I wonder if deps.dev team might be interesting in setting up something similar, obviously slightly broader in scope due to handling multiple ecosystems. My team is reliant on these corrections, as we have many deps with license metadata problems where the maintainer hasn't done a release in ~10 years, e.g. tj/callsite#9 . Even though we could publish forked packages, and use transitive dependency "overrides", in a heavily regulated industry that is a bigger headache than locally adding explicit allows in a config. It makes sense to have a global/shared list of explicit license fixups that everyone can benefit from, streamlining adoption of license tooling.

https://github.com/jslicense/spdx-correct.js to automatically correct licenses.

https://github.com/jslicense/spdx-exceptions.json in case understanding/validating spdx exceptions is a desired feature.

@cuixq
Copy link
Collaborator

cuixq commented Oct 9, 2024

@sarnesjo-google

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

No branches or pull requests

2 participants