← Home

@ohif/extension-cornerstone

OHIF extension for Cornerstone

28
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

swederikandrebotchafeydannyrbsedghiwayfarer3130

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@cornerstonejs/streaming-image-volume-loader AI (dependencies): Official Cornerstone.js ecosystem dep used by OHIF, well-vetted upstream. ai
provenance missing-githead AI (provenance): Provenance direction unchanged vs prior approved; likely tooling/CI variance, not malicious. ai
source-diff encoded-string-file:dist/ohif-extension-cornerstone.umd.js AI (source-diff): Standard webpack UMD bundle; encoded strings are base64-encoded CSS/data URIs typical of this build output, not malicious payloads. ai
phantom-deps phantom-dep:immutability-helper AI (phantom-deps): New dep added as replacement for lodash.merge; likely used indirectly through bundled code rather than direct ES import. ai
phantom-deps phantom-dep:lodash.merge AI (phantom-deps): Consumed via build config or indirect import in bundled output. ai
phantom-deps phantom-dep:shader-loader AI (phantom-deps): Webpack loader referenced in .webpack config files, not source imports. ai
phantom-deps phantom-dep:worker-loader AI (phantom-deps): Webpack loader referenced in .webpack config files, not source imports. ai
phantom-deps phantom-dep:@babel/runtime AI (phantom-deps): Framework-scoped runtime dep; consumed by transpiled output, not direct imports. ai
phantom-deps phantom-dep:lodash.compact AI (phantom-deps): Consumed via build config or indirect import in bundled output. ai
bogus-package bogus-package AI (bogus-package): Established OHIF ecosystem package; sparse README is typical for monorepo sub-packages. ai
phantom-deps phantom-dep:lodash.debounce AI (phantom-deps): Consumed via build config or indirect import in bundled output. ai
phantom-deps phantom-dep:@icr/polyseg-wasm AI (phantom-deps): Platform-specific WASM binary; loaded at runtime, not via static import. ai
phantom-deps phantom-dep:@cornerstonejs/adapters AI (phantom-deps): Cornerstone ecosystem package; may be consumed indirectly via re-exports. ai
phantom-deps phantom-dep:@itk-wasm/morphological-contour-interpolation AI (phantom-deps): Platform-specific WASM binary; loaded at runtime, not via static import. ai
phantom-deps phantom-dep:lodash.flatten AI (phantom-deps): Consumed via build config or indirect import in bundled output. ai
provenance no-provenance AI (provenance): Long-standing package predating provenance attestation; consistent with rest of OHIF monorepo. ai
phantom-deps phantom-dep:lodash.zip AI (phantom-deps): Webpack-bundled package; lodash modules may be consumed indirectly via build config. ai
phantom-deps phantom-dep:html2canvas AI (phantom-deps): Likely used via dynamic import or build config in this bundled extension. ai

Versions (showing 28 of 28)

Version Deps Published
3.13.2 19 / 1
3.13.1 19 / 1
3.13.0 19 / 1
3.12.10 18 / 0
3.12.9 18 / 0
3.12.8 18 / 0
3.12.7 18 / 0
3.12.6 18 / 0
3.12.5 18 / 0
3.12.4 18 / 0
3.12.3 18 / 0
3.12.2 18 / 0
3.12.1 18 / 0
3.12.0 18 / 0
3.11.1 17 / 0
3.11.0 17 / 0
3.10.4 17 / 0
3.10.2 17 / 0
3.10.1 17 / 0
3.10.0 17 / 0
3.9.3 11 / 1
3.9.2 11 / 1
3.9.1 11 / 1
3.9.0 11 / 1
3.8.5 12 / 1
3.8.2 12 / 1
3.8.1 12 / 1
3.8.0 12 / 1

v3.13.2

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sedghi.

v3.13.1

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sedghi.

v3.13.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sedghi.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.9.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.9.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.9.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.9.0

1 finding
INFO No provenance attestation provenance

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

v3.8.5

1 finding
INFO No provenance attestation provenance

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

v3.8.2

1 finding
INFO No provenance attestation provenance

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

v3.8.1

1 finding
INFO No provenance attestation provenance

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

v3.8.0

1 finding
INFO No provenance attestation provenance

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