@lokalise/projects-engine-contracts
API contracts and shared schemas for the Projects Engine 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Lokalise org package published via GitHub Actions; missing gitHead is a CI config change, not a security indicator. | ai | |
| dependencies | unvetted-dep:@lokalise/content-type-app-engine-contracts | AI (dependencies): Internal Lokalise org dependency consistent with this contracts package pattern; not a third-party risk. | ai | |
| phantom-deps | phantom-dep:@lokalise/api-contracts | AI (phantom-deps): Re-exported contracts package; same org scope, declared as dependency. | ai | |
| phantom-deps | phantom-dep:@lokalise/translation-storage-api-schemas | AI (phantom-deps): Re-exported contracts package; same org scope, declared as dependency. | ai | |
| phantom-deps | phantom-dep:@lokalise/content-type-app-engine-contracts | AI (phantom-deps): Re-exported contracts package; same org scope, declared as dependency. | ai | |
| provenance | no-provenance | AI (provenance): Package explicitly opts out of provenance in publishConfig; consistent Lokalise internal publishing pattern. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.8.0 | 3 / 10 | |
| 2.7.0 | 3 / 10 | |
| 2.6.1 | 3 / 10 | |
| 2.6.0 | 3 / 10 | |
| 2.5.0 | 3 / 10 | |
| 2.4.0 | 3 / 10 | |
| 2.3.2 | 3 / 10 | |
| 2.3.1 | 3 / 10 | |
| 2.3.0 | 3 / 10 | |
| 2.2.2 | 3 / 10 | |
| 2.2.1 | 3 / 10 | |
| 2.2.0 | 3 / 10 | |
| 2.1.0 | 3 / 10 | |
| 2.0.10 | 3 / 10 | |
| 2.0.8 | 3 / 10 | |
| 2.0.3 | 3 / 10 |
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.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.
v2.6.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.
v2.6.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.
v2.5.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.
v2.4.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.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.