@ohif/extension-dicom-video
OHIF extension for video display
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped package loaded by convention in transpiled code; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Config-file reference in established build-tool context; stable for this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 3.12.10 | 2 / 0 | |
| 3.12.9 | 2 / 0 | |
| 3.12.8 | 2 / 0 | |
| 3.12.7 | 2 / 0 | |
| 3.12.6 | 2 / 0 | |
| 3.12.5 | 2 / 0 | |
| 3.12.4 | 2 / 0 | |
| 3.12.3 | 2 / 0 | |
| 3.12.2 | 2 / 0 | |
| 3.12.1 | 2 / 0 | |
| 3.12.0 | 2 / 0 | |
| 3.11.1 | 2 / 0 | |
| 3.11.0 | 2 / 0 | |
| 3.10.4 | 2 / 0 | |
| 3.10.2 | 2 / 0 | |
| 3.10.1 | 2 / 0 | |
| 3.10.0 | 2 / 0 | |
| 3.9.3 | 2 / 0 | |
| 3.9.2 | 2 / 0 | |
| 3.9.1 | 2 / 0 | |
| 3.9.0 | 2 / 0 | |
| 3.8.5 | 2 / 0 | |
| 3.8.4 | 2 / 0 | |
| 3.8.3 | 2 / 0 | |
| 3.8.2 | 2 / 0 | |
| 3.8.1 | 2 / 0 | |
| 3.8.0 | 2 / 0 | |
| 3.7.0 | 2 / 0 | |
| 3.6.0 | 2 / 0 | |
| 3.5.0 | 2 / 0 | |
| 3.0.1 | 2 / 0 |
v3.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.