@lokalise/translation-storage-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, 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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Internal Lokalise org maintainer churn, no takeover indicators. | ai | |
| provenance | missing-githead | AI (provenance): CI publisher unchanged from prior approved; benign pipeline variance. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Schema package growth is expected; no exec/network behavior added. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal Lokalise schema package; missing description is a stable characteristic, not a malware signal. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from botlokalise to GitHub Actions is a CI/CD pipeline migration within the same Lokalise org; stable pattern going forward. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of michaln-lokalise aligns with org-level automation takeover of publishing; no malicious indicators. | ai | |
| provenance | no-provenance | AI (provenance): Schema library from established monorepo; provenance absence is ecosystem-wide norm. | ai | |
| dependencies | unvetted-dep:@lokalise/api-common | AI (dependencies): Same @lokalise org namespace; internal dependency consistent with the package's purpose. | ai | |
| dependencies | unvetted-dep:@lokalise/autopilot-common-api-schemas | AI (dependencies): Same @lokalise org namespace; internal dependency consistent with the package's purpose. | ai | |
| dependencies | unvetted-dep:@lokalise/common-api-schemas | AI (dependencies): Same @lokalise org namespace; internal dependency consistent with the package's purpose. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @lokalise org schema package; missing README/repo/keywords is expected for private/internal npm packages. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 16.0.0 | 7 / 6 | |
| 15.1.0 | 7 / 6 | |
| 15.0.0 | 7 / 6 | |
| 14.2.0 | 7 / 6 | |
| 14.1.0 | 7 / 6 | |
| 14.0.1 | 7 / 6 | |
| 14.0.0 | 7 / 6 | |
| 13.8.2 | 7 / 6 | |
| 13.8.1 | 7 / 6 | |
| 13.8.0 | 7 / 6 | |
| 13.7.1 | 7 / 6 | |
| 13.7.0 | 7 / 6 | |
| 13.6.0 | 7 / 6 | |
| 13.5.0 | 7 / 6 | |
| 13.4.0 | 7 / 6 | |
| 13.3.0 | 7 / 6 | |
| 13.2.0 | 7 / 6 | |
| 13.1.1 | 7 / 6 | |
| 13.1.0 | 7 / 6 | |
| 13.0.0 | 7 / 6 | |
| 12.6.1 | 7 / 6 | |
| 12.6.0 | 7 / 6 | |
| 12.5.0 | 7 / 6 | |
| 12.4.0 | 7 / 6 | |
| 12.3.1 | 7 / 6 | |
| 12.3.0 | 7 / 6 | |
| 12.2.0 | 7 / 6 | |
| 12.1.0 | 7 / 6 | |
| 12.0.0 | 7 / 6 | |
| 11.0.2 | 7 / 6 | |
| 11.0.1 | 7 / 6 | |
| 11.0.0 | 7 / 6 | |
| 10.2.1 | 7 / 6 | |
| 10.2.0 | 7 / 6 | |
| 10.1.0 | 7 / 6 | |
| 10.0.1 | 7 / 6 | |
| 10.0.0 | 7 / 6 | |
| 9.4.1 | 7 / 6 | |
| 9.4.0 | 7 / 6 | |
| 9.3.0 | 7 / 6 | |
| 9.2.0 | 7 / 6 | |
| 9.1.0 | 7 / 6 | |
| 9.0.0 | 7 / 6 | |
| 8.5.0 | 7 / 6 | |
| 8.4.0 | 7 / 6 | |
| 8.3.0 | 7 / 6 | |
| 8.2.0 | 7 / 6 | |
| 8.1.0 | 7 / 6 | |
| 8.0.0 | 7 / 6 | |
| 7.5.0 | 7 / 6 | |
| 7.4.0 | 7 / 6 |
v16.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.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.
v15.0.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.
v14.2.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.
v14.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.
v14.0.1
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.
v14.0.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.
v13.8.2
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.
v13.8.1
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.
v13.8.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.
v13.7.1
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.
v13.7.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.
v13.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.
v13.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.
v13.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.
v13.3.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.
v13.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.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.
v12.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.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.
v10.2.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.
v10.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.
v10.1.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.
v10.0.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.