@lokalise/supported-languages
5
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
bodrovismarcocardosolokbotlokalisekibertoadcarlos_gameroaplokalisefilippos.mikropoulosandrew_lokalisedariacmbezlydmitrycasamitjanabartoszdrozd-lokalisejhfedzerikapalillontrpilot-lokalise
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): CI-managed publish via GitHub Actions explains maintainer list changes, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy consistent with low-churn internal shared-lib package, provenance unchanged. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 0 / 7 | |
| 3.2.0 | 0 / 7 | |
| 3.1.1 | 0 / 9 | |
| 3.1.0 | 0 / 9 | |
| 3.0.0 | 0 / 12 |
v3.3.0
2 findings
HIGH
Missing gitHead — previous versions had it
provenance
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.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.