@lokalise/common-api-schemas
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@lokalise/zod-extras | AI (phantom-deps): Same-org schema package; declared dep may be re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@message-queue-toolkit/schemas | AI (phantom-deps): Referenced in config files per finding; stable false positive for this schema bundle. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Lokalise library; sparse README and no keywords are expected for org-internal schema packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 3 / 6 | |
| 2.2.0 | 4 / 6 | |
| 2.1.1 | 4 / 6 | |
| 2.1.0 | 4 / 6 | |
| 2.0.0 | 4 / 6 | |
| 1.6.0 | 4 / 6 | |
| 1.5.3 | 4 / 6 |
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.