@npmcli/map-workspaces
Retrieves a name:pathname Map for a given workspaces config
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established npm CLI org package; lack of Sigstore provenance is a best-practice gap, not a security risk for this well-known package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from ruyadorno to gar reflects a routine maintainer rotation within the npm/GitHub org for an official @npmcli scoped package. Both are known npm org contributors. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (fritzy, gar, lukekarrys) are known npm/GitHub org contributors. This is a standard org-level maintainer refresh for an official @npmcli package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are legacy npm contributors; removal is consistent with org-level housekeeping for this official @npmcli scoped package. | ai | |
| dependencies | unvetted-dep:@npmcli/package-json | AI (dependencies): First-party @npmcli scoped package from the official npm/GitHub org; expected dependency for this utility. Not a real risk. | ai | |
| dependencies | unvetted-dep:@npmcli/name-from-folder | AI (dependencies): First-party @npmcli scoped package from the official npm/GitHub org; expected dependency for this utility. Not a real risk. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 4 / 3 | |
| 5.0.3 | 4 / 3 | |
| 5.0.2 | 4 / 3 | |
| 5.0.1 | 4 / 3 | |
| 5.0.0 | 4 / 3 | |
| 4.0.2 | 4 / 3 | |
| 4.0.1 | 4 / 3 | |
| 4.0.0 | 4 / 3 | |
| 3.0.6 | 4 / 3 | |
| 3.0.5 | 4 / 3 | |
| 3.0.4 | 4 / 3 | |
| 3.0.3 | 4 / 3 | |
| 3.0.2 | 4 / 3 | |
| 3.0.1 | 4 / 3 | |
| 3.0.0 | 4 / 3 | |
| 2.0.4 | 4 / 3 | |
| 2.0.3 | 4 / 3 | |
| 2.0.2 | 4 / 3 | |
| 2.0.1 | 4 / 3 | |
| 2.0.0 | 4 / 4 | |
| 1.0.4 | 4 / 3 | |
| 1.0.3 | 4 / 3 | |
| 1.0.2 | 4 / 3 | |
| 1.0.1 | 4 / 3 | |
| 1.0.0 | 4 / 3 |
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.6
2 findingsThis version was published by a different npm account than previous versions on 2024-04-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.5
2 findingsThis version was published by a different npm account than previous versions on 2024-04-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.4
2 findingsThis version was published by a different npm account than previous versions on 2023-04-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsThis version was published by a different npm account than previous versions on 2023-02-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsThis version was published by a different npm account than previous versions on 2022-12-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-10-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
2 findingsThis version was published by a different npm account than previous versions on 2022-07-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsThis version was published by a different npm account than previous versions on 2022-04-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2022-02-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.