Package Exports
- validate-npm-package-license
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (validate-npm-package-license) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
validate-npm-package-license
Give me a string and I'll tell you if it's a valid npm package license string.
var noWarnings = {
validForNewPackages: true,
validForOldPackages: true
};
// SPDX license identifier for common open-source licenses
valid('MIT'); // => noWarnings
valid('BSD-2-Clause'); // => noWarnings
valid('Apache-2.0'); // => noWarnings
valid('ISC'); // => noWarnings
// Simple SPDX license expression for dual licensing
valid('(GPL-3.0 OR BSD-2-Clause)'); // => noWarnings
// Refer to a non-standard license found in the package
valid('SEE LICENSE IN LICENSE.txt'); // => noWarnings
valid('SEE LICENSE IN license.md'); // => noWarnings
// No license
valid('UNLICENSED'); // => noWarnings
valid('UNLICENCED'); // => noWarnings
var warningsWithSuggestion = {
validForOldPackages: false,
validForNewPackages: false,
warnings: [
'license should be ' +
'a valid SPDX license expression without "LicenseRef", ' +
'"UNLICENSED", or ' +
'"SEE LICENSE IN <filename>"',
'license is similar to the valid expression "Apache-2.0"'
]
};
// Almost a valid SPDX license identifier
valid('Apache 2.0'); // => warningsWithSuggestion
var warningAboutLicenseRef = {
validForOldPackages: false,
validForNewPackages: false,
warnings: [
'license should be ' +
'a valid SPDX license expression without "LicenseRef", ' +
'"UNLICENSED", or ' +
'"SEE LICENSE IN <filename>"',
]
};
// LicenseRef-* identifiers are valid SPDX expressions,
// but not valid in package.json
valid('LicenseRef-Made-Up'); // => warningAboutLicenseRef
valid('(MIT OR LicenseRef-Made-Up)'); // => warningAboutLicenseRef