@ohif/extension-dicom-microscopy
OHIF extension for DICOM microscopy
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:colormap | AI (phantom-deps): Legitimate visualization dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash.debounce | AI (phantom-deps): Utility dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@cornerstonejs/codec-charls | AI (phantom-deps): DICOM codec dep; stable false positive for this imaging extension. | ai | |
| phantom-deps | phantom-dep:@cornerstonejs/codec-openjpeg | AI (phantom-deps): DICOM codec dep; stable false positive for this imaging extension. | ai | |
| phantom-deps | phantom-dep:@cornerstonejs/codec-libjpeg-turbo-8bit | AI (phantom-deps): DICOM codec dep; stable false positive for this imaging extension. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.12.4 | 7 / 0 | |
| 3.12.3 | 7 / 0 | |
| 3.12.2 | 7 / 0 | |
| 3.12.1 | 7 / 0 | |
| 3.12.0 | 7 / 0 | |
| 3.11.1 | 7 / 0 | |
| 3.11.0 | 7 / 0 | |
| 3.10.4 | 7 / 0 | |
| 3.10.2 | 7 / 0 |
v3.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.