Closed garthk closed 7 years ago
It would be really cool if this module gets a license file + license entry in the package.json
. @chrisa @davepacheco, what do you think about it?
This sounds good to me. (There's already a LICENCE file, but we could add a field to package.json.)
Licenses are now officially a part of the package.json
spec. See here.
It would make license compliance much easier when generating reports for the suits, using tools like license-checker or npm-license-crawler.
Or advocate, which generates the most detailed report of modules you are using.
+1
Could you please use standard license? It is easier to verify MIT, ISC or any standard one that custom text. Thanks!
Resolved in b733a45.
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!