The license information in package.json is deprecated / misleading.
According to the package.json specification, an SPDX license expression 2.0 compliant license string should be provided under field license in a package.json. License objects like { type: "MIT", url: "..."} under license as well as license object arrays under licenses are deprecated.
This project has both a valid SPDX license string under license (MIT) as well as the deprecated licenses field, so removing the latter will fix the issue.
I came across this when building a tool to extract license information from all dependencies of a project and mapping them to canonical licenses. Encountering two fields carrying the same information makes it hard to decide which one to use.
The license information in package.json is deprecated / misleading.
According to the package.json specification, an SPDX license expression 2.0 compliant license string should be provided under field
license
in apackage.json
. License objects like{ type: "MIT", url: "..."}
underlicense
as well as license object arrays underlicenses
are deprecated.This project has both a valid SPDX license string under
license
(MIT) as well as the deprecatedlicenses
field, so removing the latter will fix the issue.I came across this when building a tool to extract license information from all dependencies of a project and mapping them to canonical licenses. Encountering two fields carrying the same information makes it hard to decide which one to use.