-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Publish to NPM with proper LICENSE metadata. #7
Comments
And it's kinda funny, but Git states that the license is BSD 2 Clause, but the text is BSD 3 Clause. |
@hrieke, also the text is BSD 2 Clause, see how the third "Neither the name of the copyright holder nor [...]" clause is missing. It's just that the formatting is a bit off. |
The license is the BSD-2-Clause. I would be surprised if this even passes the bar for copyright protection. My goal with this library was to publish a single version, then leave it as it is. I doubt there will be a new release in the foreseeable future. |
The newest version of this package on NPM still specifies "license: none" (https://www.npmjs.com/package/domelementtype).
Can you publish a new version to NPM which has the proper license tag in package.json (This is already included in master, but the version is not published yet).
Having proper license metadata helps managing large projects with complex dependencies. Currently, when using, e.g., https://github.com/iandotkelly/nlf, this package shows up as a false positive, since the license cannot be automatically detected.
The text was updated successfully, but these errors were encountered: