-
Notifications
You must be signed in to change notification settings - Fork 35
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 "license" and "licenses" to package.json #8
Comments
The |
If interested, I can create a PR for this. |
I have seen there is little progress on this project over the past few years. My project, the net-snmp project, depends on this project, so I have cloned it and migrated (i.e. copied) all the outstanding issues and pull requests. I will be releasing a new version of my version of this project under the asn1-ber namespace on npmjs.org by the end of the week which should address this particular item (I've already pushed the current code to this namespace to reserve it). I am now tracking all changes under my own copy at asn1-ber. Note that this is not a "fork" but a clone and fresh commit to a new repository. I have of course retained all copyrights and attributed back the original author. There are quite a few projects dependant on this project, and I want to make sure there is momentum on the issues and feature requests reported. |
This issue has been addressed in my version of this project which has now been published to npm: |
Specifying your license in
package.json
makes it a lot easier for your users to find and comply with GNU Affero licenses.Also giving
licenses
(an array of objects withtype
andurl
keys) helps users whose legal departments request both the license name and the text. See this example from async:Though
licenses
isn't specified in the npm package.json spec, it is supported by the NPM site, as you'll see if you check async's NPM page.Thanks!
The text was updated successfully, but these errors were encountered: