@lokalise/tm-api-schemas
API schemas for 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): CI-published package, metadata drift not malicious behavior. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Single maintainer removal, no new suspicious maintainer added. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from botlokalise to GitHub Actions reflects internal CI/CD migration within Lokalise org; stable pattern going forward. | ai | |
| dependencies | unvetted-dep:@lokalise/common-api-schemas | AI (dependencies): Same Lokalise org namespace; consistent with the package's other @lokalise/* dependencies. | ai | |
| provenance | no-provenance | AI (provenance): Org-published package via GitHub Actions; provenance absence is common and not a risk indicator here. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 6.3.0 | 4 / 7 | |
| 6.2.0 | 4 / 7 | |
| 6.1.1 | 4 / 7 | |
| 6.1.0 | 4 / 7 | |
| 6.0.0 | 4 / 7 | |
| 5.7.0 | 4 / 7 | |
| 5.6.1 | 4 / 7 | |
| 5.6.0 | 4 / 7 | |
| 5.5.4 | 4 / 7 | |
| 5.5.3 | 4 / 7 | |
| 5.5.2 | 4 / 7 | |
| 5.5.1 | 4 / 7 | |
| 5.5.0 | 4 / 7 | |
| 5.4.0 | 4 / 7 | |
| 5.3.0 | 4 / 7 | |
| 5.2.0 | 4 / 7 | |
| 5.1.0 | 4 / 7 | |
| 5.0.1 | 4 / 7 | |
| 5.0.0 | 4 / 7 | |
| 4.4.0 | 4 / 7 | |
| 4.3.0 | 4 / 7 | |
| 4.2.0 | 4 / 7 | |
| 4.1.0 | 4 / 7 | |
| 4.0.0 | 4 / 7 | |
| 3.3.0 | 4 / 7 | |
| 3.2.0 | 4 / 7 | |
| 3.1.0 | 4 / 7 |
v6.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.
v6.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.
v6.1.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.
v6.1.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.