@radicalimaging/static-wado-scp
DimseScp server to connect to static-wado repo
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@radicalimaging/static-wado-creator | AI (dependencies): Same-org monorepo dependency; consistent pattern across all @radicalimaging packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.7.2 | 6 / 1 | |
| 1.7.0 | 6 / 1 | |
| 1.6.10 | 6 / 1 | |
| 1.6.8 | 6 / 1 | |
| 1.6.7 | 6 / 1 | |
| 1.6.6 | 6 / 1 |
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.