@logto/translate
A CLI tool that helps translate phrases and experience-phrases to i18n resources.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@logto/language-kit | AI (dependencies): Same @logto org scope as this package; consistent publisher lineage. | ai | |
| phantom-deps | phantom-dep:@logto/core-kit | AI (phantom-deps): @logto/core-kit is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.2.14 | 16 / 9 | |
| 0.2.13 | 16 / 9 | |
| 0.2.12 | 16 / 9 | |
| 0.2.11 | 16 / 9 | |
| 0.2.10 | 16 / 9 | |
| 0.2.9 | 16 / 9 | |
| 0.2.8 | 16 / 9 | |
| 0.2.7 | 16 / 9 | |
| 0.2.6 | 16 / 9 | |
| 0.2.5 | 16 / 9 | |
| 0.2.4 | 16 / 9 | |
| 0.2.3 | 16 / 9 | |
| 0.2.2 | 16 / 9 | |
| 0.2.1 | 16 / 9 |
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (simeng_li) than the most recent previously approved version (gaosun) on 2026-05-29, but simeng_li is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.