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 SPDX License Identifier to package.json #81

Open
szimmer-dap opened this issue May 22, 2024 · 0 comments
Open

Add SPDX License Identifier to package.json #81

szimmer-dap opened this issue May 22, 2024 · 0 comments

Comments

@szimmer-dap
Copy link

Hi there!

We are currently adapting a package approval workflow, where packages are approved or blocked based on certain criteria. One very important criterion is the package's license. There is a list of approved licenses (like MIT, Apache, ...) and a list of licenses that can not be used (like GPL).

Although your package seems to be under MIT license, it's hard to auto-approve them, because they don't use an SPDX tag (https://spdx.github.io/spdx-spec/v2-draft/SPDX-license-list/). As a result, the license does not show up in the package's metadata (compare e.g. info section of https://www.npmjs.com/package/union with https://www.npmjs.com/package/@angular/core, where the latter clearly states the package's license, while yours does not).

Would you consider using an SPDX license expression? Basically, all that is needed is a license entry in the package.json file.
See https://docs.npmjs.com/cli/v10/configuring-npm/package-json#license for reference.
In fact, it seems that there is actually an open pull request for this already.

Additional LICENSE files or license infos in README files can remain as they are (as long as they don't contradict the content of the "license" entry).

This would be a huge help for us, because without license information within packages' metadata we have to manually check and approve every single version of every package.

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

1 participant