@ohif/mode-preclinical-4d
4D Workflow
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
Keywords
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.12.10 | 1 / 2 | |
| 3.12.9 | 1 / 2 | |
| 3.12.8 | 1 / 2 | |
| 3.12.7 | 1 / 2 | |
| 3.12.6 | 1 / 2 | |
| 3.12.5 | 1 / 2 | |
| 3.12.4 | 1 / 2 | |
| 3.12.3 | 1 / 2 | |
| 3.12.2 | 1 / 2 | |
| 3.12.1 | 1 / 2 | |
| 3.12.0 | 1 / 2 | |
| 3.11.1 | 1 / 2 | |
| 3.11.0 | 1 / 2 | |
| 3.10.4 | 1 / 2 | |
| 3.10.2 | 1 / 2 | |
| 3.10.1 | 1 / 2 | |
| 3.10.0 | 1 / 2 | |
| 3.9.3 | 1 / 2 | |
| 3.9.2 | 1 / 2 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.