← Home

@ohif/extension-cornerstone-dicom-seg

npm Repository

DICOM SEG read workflow

31
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

Keywords

ohif-extension

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file-transition:dist/ohif-extension-cornerstone-dicom-seg.umd.js AI (source-diff): Bundled new legit deps (cornerstonejs/vtk.js) into UMD build; boilerplate, not a dropper. ai
source-diff source-size-tripled AI (source-diff): Size increase matches newly bundled cornerstonejs/vtk.js dependencies. ai
phantom-deps phantom-dep:react-color AI (phantom-deps): Listed as a direct dependency in package.json; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@babel/runtime AI (phantom-deps): Framework-scoped transitive dep; stable false positive for this package. ai
phantom-deps phantom-dep:@kitware/vtk.js AI (phantom-deps): Listed as a direct dependency in package.json; phantom-dep heuristic false positive for this package. ai

Versions (showing 31 of 31)

Version Deps Published
3.12.10 4 / 0
3.12.9 4 / 0
3.12.8 4 / 0
3.12.7 4 / 0
3.12.6 4 / 0
3.12.5 4 / 0
3.12.4 4 / 0
3.12.3 4 / 0
3.12.2 4 / 0
3.12.1 4 / 0
3.12.0 5 / 0
3.11.1 5 / 0
3.11.0 5 / 0
3.10.4 5 / 0
3.10.2 5 / 0
3.10.1 5 / 0
3.10.0 5 / 0
3.9.3 5 / 0
3.9.2 5 / 0
3.9.1 5 / 0
3.9.0 5 / 0
3.8.5 5 / 0
3.8.4 5 / 0
3.8.3 5 / 0
3.8.2 5 / 0
3.8.1 5 / 0
3.8.0 5 / 0
3.7.0 5 / 0
3.6.0 2 / 0
3.5.0 2 / 21
3.0.0 2 / 21

v3.12.10

1 finding
LOW No provenance attestation provenance

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

v3.12.9

1 finding
LOW No provenance attestation provenance

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

v3.12.8

1 finding
LOW No provenance attestation provenance

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

v3.12.7

1 finding
LOW No provenance attestation provenance

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

v3.12.6

1 finding
LOW No provenance attestation provenance

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

v3.10.1

1 finding
LOW No provenance attestation provenance

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

v3.10.0

1 finding
LOW No provenance attestation provenance

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

v3.9.3

1 finding
LOW No provenance attestation provenance

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

v3.9.2

1 finding
LOW No provenance attestation provenance

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

v3.9.1

1 finding
LOW No provenance attestation provenance

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

v3.9.0

1 finding
LOW No provenance attestation provenance

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

v3.8.5

1 finding
LOW No provenance attestation provenance

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

v3.8.4

1 finding
LOW No provenance attestation provenance

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

v3.8.3

1 finding
LOW No provenance attestation provenance

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

v3.8.2

1 finding
LOW No provenance attestation provenance

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

v3.8.1

1 finding
LOW No provenance attestation provenance

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

v3.8.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.

v3.7.0

2 findings
HIGH Modified file gained network + code execution: dist/ohif-extension-cornerstone-dicom-seg.umd.js source-diff

This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.

LOW No provenance attestation provenance

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

v3.6.0

1 finding
LOW No provenance attestation provenance

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

v3.5.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.

v3.0.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.