Update Licence field in package.json to match LICENSE file #127
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.
In the
package.json
, this project had"license": "New Relic"
, which is not a valid license type that I'm aware of. I am working on a mobile app for an enterprise client that does dependency analysis to ensure all of our dependencies are permissable for use in their organization, and the tool flagged this project due to the unrecognized license.This PR just updates the field to be "Apache-2.0" to match the license specified in the LICENSE file.