@lokalise/tm-sdk
REST API client for the Lokalise Translation Memory 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, 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): Org switched to GitHub Actions CI publish; missing gitHead reflects pipeline change, not supply-chain compromise. | ai | |
| dependencies | unvetted-dep:@lokalise/id-utils | AI (dependencies): Same-org (@lokalise) dependency; consistent with the package's established dependency pattern. | ai | |
| provenance | no-provenance | AI (provenance): Lokalise org package with consistent publishing history; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@lokalise/id-utils | AI (phantom-deps): Same-org dep; may be used transitively rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@lokalise/api-common | AI (phantom-deps): Same-org dep; may be used transitively rather than directly imported. | ai | |
| phantom-deps | phantom-dep:undici | AI (phantom-deps): Known implicit runtime dependency pattern; stable for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 11.4.0 | 7 / 11 | |
| 11.3.0 | 7 / 11 | |
| 11.2.1 | 7 / 11 | |
| 11.2.0 | 8 / 11 | |
| 11.1.0 | 8 / 11 | |
| 11.0.0 | 8 / 11 | |
| 10.8.0 | 8 / 11 | |
| 10.7.1 | 8 / 11 | |
| 10.7.0 | 8 / 11 | |
| 10.6.4 | 8 / 11 | |
| 10.6.3 | 8 / 11 | |
| 10.6.2 | 8 / 11 | |
| 10.6.1 | 8 / 11 | |
| 10.6.0 | 8 / 11 | |
| 10.5.0 | 8 / 11 | |
| 10.4.0 | 8 / 11 | |
| 10.3.0 | 8 / 11 | |
| 10.2.0 | 8 / 11 | |
| 10.1.1 | 8 / 11 | |
| 10.1.0 | 8 / 11 | |
| 10.0.1 | 8 / 11 | |
| 10.0.0 | 8 / 11 | |
| 9.1.0 | 8 / 11 |
v11.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
2 findings[Accepted risk] Package 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: GitHub Actions.
v11.2.1
2 findings[Accepted risk] Package 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: GitHub Actions.
v11.2.0
2 findings[Accepted risk] Package 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: GitHub Actions.
v10.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.