@lokalise/translation-storage-api-schemas
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal Lokalise schema package; missing description is a stable characteristic, not a malware signal. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from botlokalise to GitHub Actions is a CI/CD pipeline migration within the same Lokalise org; stable pattern going forward. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of michaln-lokalise aligns with org-level automation takeover of publishing; no malicious indicators. | ai | |
| provenance | no-provenance | AI (provenance): Schema library from established monorepo; provenance absence is ecosystem-wide norm. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @lokalise org schema package; missing README/repo/keywords is expected for private/internal npm packages. | ai | |
| dependencies | unvetted-dep:@lokalise/autopilot-common-api-schemas | AI (dependencies): Same @lokalise org namespace; internal dependency consistent with the package's purpose. | ai | |
| dependencies | unvetted-dep:@lokalise/common-api-schemas | AI (dependencies): Same @lokalise org namespace; internal dependency consistent with the package's purpose. | ai | |
| dependencies | unvetted-dep:@lokalise/api-common | AI (dependencies): Same @lokalise org namespace; internal dependency consistent with the package's purpose. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 11.0.1 | 7 / 6 | |
| 10.0.0 | 7 / 6 | |
| 9.4.1 | 7 / 6 | |
| 9.4.0 | 7 / 6 | |
| 9.3.0 | 7 / 6 | |
| 9.2.0 | 7 / 6 | |
| 9.1.0 | 7 / 6 | |
| 9.0.0 | 7 / 6 | |
| 8.5.0 | 7 / 6 | |
| 8.4.0 | 7 / 6 | |
| 8.3.0 | 7 / 6 | |
| 8.2.0 | 7 / 6 | |
| 8.1.0 | 7 / 6 | |
| 8.0.0 | 7 / 6 | |
| 7.5.0 | 7 / 6 | |
| 7.4.0 | 7 / 6 | |
| 7.3.0 | 7 / 6 | |
| 7.2.0 | 7 / 6 | |
| 7.1.1 | 7 / 6 | |
| 7.1.0 | 7 / 6 | |
| 7.0.0 | 7 / 6 | |
| 6.1.0 | 7 / 6 | |
| 6.0.0 | 7 / 6 | |
| 5.0.0 | 7 / 6 | |
| 4.4.0 | 7 / 6 | |
| 4.3.0 | 7 / 6 | |
| 4.2.0 | 7 / 6 | |
| 4.1.0 | 7 / 6 | |
| 4.0.0 | 7 / 6 | |
| 3.4.0 | 7 / 6 | |
| 3.3.0 | 7 / 6 | |
| 3.2.0 | 7 / 6 | |
| 3.1.1 | 7 / 6 | |
| 3.1.0 | 7 / 6 | |
| 3.0.0 | 7 / 6 | |
| 2.2.3 | 7 / 6 | |
| 2.2.2 | 7 / 6 | |
| 2.2.1 | 7 / 6 | |
| 2.2.0 | 6 / 6 | |
| 2.1.0 | 6 / 6 | |
| 2.0.1 | 6 / 6 | |
| 2.0.0 | 6 / 6 | |
| 1.13.0 | 6 / 6 | |
| 1.12.0 | 6 / 6 | |
| 1.11.0 | 6 / 6 | |
| 1.10.1 | 6 / 6 | |
| 1.10.0 | 6 / 6 | |
| 1.9.1 | 6 / 6 | |
| 1.9.0 | 6 / 6 | |
| 1.8.0 | 6 / 6 | |
| 1.7.1 | 6 / 6 |
v11.0.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: GitHub Actions.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.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: GitHub Actions.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.