@radicalimaging/static-wado-util
Utils for other packages.
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Long strings are DICOM data dictionary blobs (tag names, VR tables) bundled by the build; not obfuscation. | ai | |
| phantom-deps | phantom-dep:json5 | AI (phantom-deps): Config-file reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:jpeg-lossless-decoder-js | AI (phantom-deps): Codec plugin declared for optional use; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:must | AI (phantom-deps): must is in devDependencies; phantom-dep false positive for test assertion library. | ai | |
| phantom-deps | phantom-dep:@cornerstonejs/codec-openjph | AI (phantom-deps): Codec plugin declared for optional use; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@cornerstonejs/codec-openjpeg | AI (phantom-deps): Codec plugin declared for optional use; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@cornerstonejs/dicom-codec | AI (phantom-deps): Codec plugin declared for optional use; not directly imported by design. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.7.6 | 12 / 0 | |
| 1.7.4 | 12 / 0 | |
| 1.7.3 | 12 / 0 | |
| 1.7.2 | 12 / 0 | |
| 1.7.0 | 11 / 0 | |
| 1.6.12 | 10 / 0 | |
| 1.6.11 | 10 / 0 | |
| 1.6.10 | 10 / 0 | |
| 1.6.9 | 10 / 0 | |
| 1.6.8 | 10 / 0 | |
| 1.6.7 | 9 / 0 | |
| 1.6.6 | 9 / 0 |
v1.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
2 findingsModified file contains 12 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
2 findingsModified file contains 12 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.