@ohif/mode-longitudinal
Longitudinal 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): Used by convention in OHIF i18n setup, not directly imported in this mode package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Standard Babel helper dep, loaded by convention. | ai | |
| provenance | missing-githead | AI (provenance): Monorepo publish pipeline artifact, consistent with unchanged provenance direction. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.13.2 | 2 / 2 | |
| 3.13.1 | 2 / 2 | |
| 3.13.0 | 2 / 2 | |
| 3.12.10 | 2 / 2 | |
| 3.12.9 | 2 / 2 | |
| 3.12.8 | 2 / 2 | |
| 3.12.7 | 2 / 2 | |
| 3.12.6 | 2 / 2 | |
| 3.12.5 | 2 / 2 | |
| 3.12.4 | 2 / 2 | |
| 3.12.3 | 2 / 2 | |
| 3.12.2 | 2 / 2 | |
| 3.12.1 | 2 / 2 | |
| 3.12.0 | 2 / 2 | |
| 3.11.1 | 2 / 2 | |
| 3.11.0 | 2 / 2 | |
| 3.10.4 | 2 / 2 | |
| 3.10.2 | 2 / 2 | |
| 3.10.1 | 2 / 2 | |
| 3.10.0 | 2 / 2 | |
| 3.9.3 | 2 / 2 | |
| 3.9.2 | 2 / 2 | |
| 3.9.1 | 2 / 2 | |
| 3.9.0 | 2 / 2 | |
| 3.8.5 | 2 / 2 | |
| 3.8.4 | 2 / 2 | |
| 3.8.3 | 2 / 2 | |
| 3.8.2 | 2 / 2 | |
| 3.8.1 | 2 / 2 | |
| 3.8.0 | 2 / 2 | |
| 3.7.0 | 1 / 2 | |
| 3.6.0 | 1 / 2 | |
| 3.5.0 | 1 / 2 | |
| 3.0.0 | 1 / 2 |
v3.13.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sedghi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sedghi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.