Specify license on package.json #42
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hey there, We're using an automated tool called License Finder (https://github.com/pivotal/LicenseFinder) and your node module coms up as "Unknown". By adding the license to package.json you would help immensely users of this and other automated tools to figure out whether a module can be used inside another project. Thanks!
|
+1 |
1 similar comment
|
👍 |
rauchg
added a commit
that referenced
this pull request
May 25, 2015
Specify license on package.json
|
Could you please make a new release for this as soon as possible? |
|
+1, please release |
38 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey there,
We're using an automated tool called License Finder (https://github.com/pivotal/LicenseFinder) and your node module comes up as "Unknown". By adding the license to package.json you would help immensely users of this and other automated tools to figure out whether a module can be used inside another project.
Thanks!