@strapi/cloud-cli
Commands to interact with the Strapi Cloud
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): alexandrebodin is a long-standing Strapi team member (3230 days, 12955 approved). Publisher rotation within the Strapi org is expected. | ai | |
| dependencies | unvetted-dep:xdg-app-paths | AI (dependencies): xdg-app-paths is a legitimate utility for XDG base directory resolution; appropriate and expected for a CLI tool like @strapi/cloud-cli. | ai | |
| provenance | no-provenance | AI (provenance): Strapi's established publishing pipeline does not use Sigstore provenance; this is consistent across all their packages and not a risk indicator. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard Strapi license declaration pattern used across their entire monorepo; not a risk indicator. | ai |
Versions (showing 100 of 112)
| Version | Deps | Published |
|---|---|---|
| 5.51.0 | 20 / 8 | |
| 5.50.2 | 20 / 8 | |
| 5.50.1 | 20 / 5 | |
| 5.50.0 | 20 / 5 | |
| 5.49.0 | 20 / 5 | |
| 5.48.1 | 20 / 5 | |
| 5.48.0 | 20 / 5 | |
| 5.47.1 | 20 / 5 | |
| 5.47.0 | 20 / 5 | |
| 5.46.1 | 20 / 5 | |
| 5.46.0 | 20 / 5 | |
| 5.45.1 | 20 / 5 | |
| 5.45.0 | 20 / 5 | |
| 5.44.0 | 20 / 5 | |
| 5.43.0 | 20 / 5 | |
| 5.42.1 | 20 / 5 | |
| 5.42.0 | 20 / 5 | |
| 5.41.1 | 20 / 5 | |
| 5.41.0 | 20 / 5 | |
| 5.40.0 | 20 / 5 | |
| 5.39.0 | 20 / 5 | |
| 5.38.1 | 20 / 5 | |
| 5.38.0 | 20 / 5 | |
| 5.37.1 | 20 / 5 | |
| 5.37.0 | 20 / 5 | |
| 5.36.1 | 20 / 5 | |
| 5.36.0 | 20 / 5 | |
| 5.35.0 | 20 / 5 | |
| 5.34.0 | 20 / 5 | |
| 5.33.4 | 20 / 5 | |
| 5.33.3 | 20 / 5 | |
| 5.33.2 | 20 / 5 | |
| 5.33.1 | 20 / 5 | |
| 5.33.0 | 20 / 5 | |
| 5.32.0 | 20 / 5 | |
| 5.31.3 | 20 / 5 | |
| 5.31.2 | 20 / 5 | |
| 5.31.1 | 20 / 5 | |
| 5.31.0 | 20 / 5 | |
| 5.30.1 | 20 / 5 | |
| 5.30.0 | 20 / 5 | |
| 5.29.0 | 20 / 5 | |
| 5.28.0 | 20 / 5 | |
| 5.27.0 | 20 / 5 | |
| 5.26.0 | 20 / 5 | |
| 5.25.0 | 20 / 5 | |
| 5.24.2 | 20 / 5 | |
| 5.24.1 | 20 / 5 | |
| 5.24.0 | 20 / 5 | |
| 5.23.6 | 20 / 5 | |
| 5.23.5 | 20 / 5 | |
| 5.23.4 | 20 / 5 | |
| 5.23.3 | 20 / 5 | |
| 5.23.2 | 20 / 5 | |
| 5.23.1 | 20 / 5 | |
| 5.23.0 | 20 / 5 | |
| 5.22.0 | 20 / 5 | |
| 5.21.0 | 20 / 5 | |
| 5.20.0 | 20 / 5 | |
| 5.19.0 | 20 / 5 | |
| 5.18.1 | 20 / 5 | |
| 5.18.0 | 20 / 5 | |
| 5.17.0 | 20 / 5 | |
| 5.16.1 | 20 / 5 | |
| 5.16.0 | 20 / 5 | |
| 5.15.1 | 20 / 5 | |
| 5.15.0 | 20 / 5 | |
| 5.14.0 | 20 / 5 | |
| 5.13.1 | 20 / 5 | |
| 5.13.0 | 20 / 5 | |
| 5.12.7 | 20 / 5 | |
| 5.12.6 | 20 / 5 | |
| 5.12.5 | 20 / 5 | |
| 5.12.4 | 20 / 5 | |
| 5.12.3 | 20 / 5 | |
| 5.12.2 | 20 / 5 | |
| 5.12.1 | 20 / 5 | |
| 5.12.0 | 20 / 5 | |
| 5.11.3 | 20 / 5 | |
| 5.11.2 | 20 / 5 | |
| 5.11.1 | 20 / 5 | |
| 5.11.0 | 20 / 5 | |
| 5.10.4 | 20 / 5 | |
| 5.10.3 | 20 / 5 | |
| 5.10.2 | 20 / 5 | |
| 5.10.1 | 20 / 5 | |
| 5.10.0 | 20 / 5 | |
| 5.9.0 | 20 / 6 | |
| 5.8.1 | 20 / 6 | |
| 5.8.0 | 20 / 6 | |
| 5.7.0 | 20 / 6 | |
| 5.6.0 | 20 / 6 | |
| 5.5.2 | 20 / 6 | |
| 5.5.1 | 20 / 6 | |
| 5.5.0 | 20 / 6 | |
| 5.4.2 | 20 / 6 | |
| 5.4.1 | 20 / 6 | |
| 5.4.0 | 19 / 6 | |
| 5.3.0 | 19 / 6 | |
| 5.2.0 | 19 / 6 |
v5.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.50.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.50.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.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.
v5.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.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.
v5.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.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.
v5.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.