@lokalise/polyglot-sdk
REST API client for the Lokalise Polyglot service
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org @lokalise/api-contracts; consistent with Lokalise SDK evolution pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established Lokalise org package; lack of provenance is consistent across all versions and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@lokalise/id-utils | AI (dependencies): Same-org @lokalise scoped dependency; consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@lokalise/fastify-extras | AI (dependencies): Same-org @lokalise scoped dependency; consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@lokalise/non-translatable-markup | AI (dependencies): Same-org @lokalise scoped dependency; consistent with this package's ecosystem. | ai | |
| phantom-deps | phantom-dep:@lokalise/id-utils | AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for internal SDK packages. | ai | |
| phantom-deps | phantom-dep:undici | AI (phantom-deps): undici is a declared runtime dep; phantom-dep false positive for indirect usage patterns. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 24.2.0 | 12 / 13 | |
| 24.1.0 | 11 / 13 | |
| 23.0.3 | 10 / 13 | |
| 23.0.2 | 10 / 13 | |
| 23.0.1 | 10 / 13 | |
| 23.0.0 | 10 / 13 | |
| 22.12.1 | 10 / 13 | |
| 22.12.0 | 10 / 13 | |
| 22.11.3 | 10 / 13 | |
| 22.11.1 | 10 / 13 | |
| 22.10.0 | 10 / 13 | |
| 22.9.3 | 10 / 13 | |
| 22.9.2 | 10 / 13 | |
| 22.9.1 | 10 / 13 | |
| 22.9.0 | 10 / 13 | |
| 22.8.0 | 10 / 13 | |
| 22.7.1 | 10 / 13 | |
| 22.7.0 | 10 / 13 | |
| 22.6.1 | 10 / 13 |
v24.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.