← Home

@lokalise/translation-api-schemas

This library contains API contracts, schemas and types related to the translation domain. This includes: * AI Configuration * Translation Quality Score

27
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

bodrovismarcocardosolokbotlokalisekibertoadcarlos_gameroaplokalisefilippos.mikropoulosandrew_lokalisedariacmbezlydmitrycasamitjanabartoszdrozd-lokalisejhfedzerikapalillontrpilot-lokalise

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from botlokalise to GitHub Actions is an internal Lokalise CI/CD migration; both are org-controlled automation accounts. ai
provenance no-provenance AI (provenance): Lokalise org packages consistently lack Sigstore provenance; stable false positive for this publisher. ai
bogus-package bogus-package AI (bogus-package): Scoped org package; sparse README and missing keywords are cosmetic, not spam indicators. ai

Versions (showing 27 of 27)

Version Deps Published
3.15.2 1 / 2
3.15.1 1 / 2
3.15.0 1 / 2
3.14.0 1 / 2
3.13.0 1 / 2
3.12.1 1 / 2
3.12.0 1 / 2
3.11.0 1 / 2
3.10.0 1 / 2
3.9.0 1 / 2
3.8.4 1 / 2
3.8.3 1 / 2
3.8.2 1 / 2
3.8.1 1 / 2
3.8.0 1 / 2
3.7.0 1 / 2
3.6.0 1 / 2
3.5.0 1 / 2
3.4.0 1 / 2
3.3.0 1 / 2
3.2.0 1 / 2
3.1.0 1 / 2
3.0.0 1 / 2
2.6.3 1 / 2
2.6.2 1 / 2
2.6.1 1 / 2
2.6.0 1 / 2

v3.15.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.15.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.15.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.14.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.13.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.