@cornerstonejs/labelmap-interpolation
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Org-level maintainer rotation within cornerstonejs; publisher sedghi has strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added; consistent with team roster change in established org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Cornerstone3D monorepo; version gaps are normal for sub-packages that only publish with coordinated releases. | ai | |
| dependencies | unvetted-dep:itk-wasm | AI (dependencies): itk-wasm is the standard ITK WebAssembly toolkit; expected dependency for medical imaging interpolation. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.22.13 | 2 / 2 | |
| 4.21.1 | 2 / 0 | |
| 4.20.1 | 2 / 0 | |
| 4.15.29 | 2 / 0 | |
| 4.15.4 | 2 / 0 | |
| 4.5.9 | 2 / 0 | |
| 4.3.15 | 2 / 0 | |
| 4.2.3 | 2 / 0 | |
| 4.2.2 | 2 / 0 | |
| 4.1.1 | 2 / 0 |
v4.22.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.