@ohif/i18n
Internationalization library for The OHIF Viewer
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo CI publish pattern for trusted long-standing publisher, not a compromise indicator. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Consistent with monorepo lockstep releases across many packages. | ai | |
| phantom-deps | phantom-dep:locize-editor | AI (phantom-deps): Used via config files, not direct import; stable pattern for this i18n package. | ai | |
| phantom-deps | phantom-dep:locize-lastused | AI (phantom-deps): Used via config files, not direct import; stable pattern for this i18n package. | ai | |
| phantom-deps | phantom-dep:i18next-locize-backend | AI (phantom-deps): Used via config files, not direct import; stable pattern for this i18n package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dep; loaded by convention, not direct import. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.13.2 | 4 / 7 | |
| 3.13.1 | 4 / 7 | |
| 3.13.0 | 4 / 7 | |
| 3.12.10 | 4 / 6 | |
| 3.12.9 | 4 / 6 | |
| 3.12.8 | 4 / 6 | |
| 3.12.7 | 4 / 6 | |
| 3.12.6 | 4 / 6 | |
| 3.12.5 | 4 / 6 | |
| 3.12.4 | 4 / 6 | |
| 3.12.3 | 4 / 6 | |
| 3.12.2 | 4 / 6 | |
| 3.12.1 | 4 / 6 | |
| 3.12.0 | 4 / 6 | |
| 3.11.1 | 4 / 6 | |
| 3.11.0 | 4 / 6 | |
| 3.10.4 | 4 / 6 | |
| 3.10.2 | 4 / 6 | |
| 3.10.1 | 4 / 6 | |
| 3.10.0 | 4 / 6 | |
| 3.9.3 | 4 / 6 | |
| 3.9.2 | 4 / 6 | |
| 3.9.1 | 4 / 6 | |
| 3.9.0 | 4 / 6 | |
| 3.8.5 | 4 / 6 | |
| 3.8.4 | 4 / 6 | |
| 3.8.3 | 4 / 6 | |
| 3.8.2 | 4 / 6 | |
| 3.8.1 | 4 / 6 | |
| 3.8.0 | 4 / 6 | |
| 3.7.0 | 4 / 6 | |
| 3.6.0 | 4 / 6 | |
| 3.5.0 | 4 / 6 | |
| 3.0.0 | 4 / 6 |
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.