fix: handle legacy licenses array in sbom output#9010
Merged
wraithgar merged 1 commit intonpm:latestfrom Feb 24, 2026
Merged
Conversation
Packages using the deprecated `licenses` array property in
package.json (e.g. `"licenses": [{"type": "MIT", "url": "..."}]`)
were reported as NOASSERTION in both SPDX and CycloneDX SBOM output.
This adds support for the legacy format by checking for the `licenses`
array when `license` is not present, joining multiple entries with
" OR " per SPDX conventions.
Closes npm#8892
JNC4
force-pushed
the
fix/sbom-legacy-licenses
branch
from
35e5817 to
e7ad380
Compare
wraithgar
approved these changes
Feb 24, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #8892
Older packages on the registry use the deprecated
licensesarray ("licenses": [{"type": "MIT", ...}]) instead of the singularlicensestring.npm sbomonly checked forlicense, so these packages all showed up asNOASSERTION.This checks for the
licensesarray as a fallback in both the SPDX and CycloneDX codepaths. When there are multiple entries they're joined withOR.Also noticed the CycloneDX expression branch was referencing
node.package.licensedirectly instead of the already-computed variable, which would break for these legacy packages. Fixed that too.