← Home

@radicalimaging/static-wado-webserver

npm Repository Homepage

Webserver to serve a static-wado repo

10
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

wayfarer3130sedghipedrokohler-radical

Keywords

StaticWadoStaticWadoServerDICOMDICOMweb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Passing process.env to a spawned subprocess is standard for a server monitor; no exfiltration path. ai
semgrep semgrep:child-process-import AI (semgrep): child_process is used legitimately to spawn the DICOM web server process; expected for this package. ai
phantom-deps phantom-dep:@radicalimaging/static-wado-webserver AI (phantom-deps): Self-referential same-org dep; phantom-dep heuristic false positive for this package. ai

Versions (showing 10 of 10)

Version Deps Published
1.7.4 18 / 3
1.7.3 18 / 3
1.7.0 14 / 3
1.6.12 11 / 2
1.6.11 11 / 2
1.6.10 11 / 2
1.6.9 11 / 2
1.6.8 11 / 2
1.6.7 11 / 2
1.6.6 11 / 2

v1.7.4

2 findings
HIGH env-spread: bin/monitordicomwebserver.mjs:38 semgrep

Spreading entire process.env into an object — may capture all secrets 36 | serverProcess = spawn('bun', args, { 37 | stdio: ['inherit', 'pipe', 'pipe'], > 38 | env: { ...process.env } 39 | }); 40 |

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.3

2 findings
HIGH env-spread: bin/monitordicomwebserver.mjs:38 semgrep

Spreading entire process.env into an object — may capture all secrets 36 | serverProcess = spawn('bun', args, { 37 | stdio: ['inherit', 'pipe', 'pipe'], > 38 | env: { ...process.env } 39 | }); 40 |

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.