@strapi/plugin-cloud
Instructions to deploy your local project to 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 — 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@strapi/helper-plugin | AI (dependencies): First-party Strapi package; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/_chunks/App-D-wfuQOx.js | AI (source-diff): Standard bundled/minified React JSX output for Strapi admin plugin. | ai | |
| source-diff | obfuscated-file:dist/_chunks/App-BREN5NnX.mjs | AI (source-diff): ESM counterpart of the same bundled admin UI; not obfuscated. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Strapi monorepo plugin; inactivity reflects upstream release cadence, not account takeover. | ai | |
| dependencies | unvetted-dep:@strapi/icons | AI (dependencies): @strapi/icons is a first-party Strapi organization package; unvetted status is a pipeline artifact, not a security concern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Short README and no keywords are typical of internal monorepo plugin packages; this is a legitimate, well-established Strapi plugin with 90k+ weekly downloads. | ai | |
| dependencies | unvetted-dep:@strapi/design-system | AI (dependencies): @strapi/design-system is a first-party Strapi organization package; unvetted status is a pipeline artifact, not a security concern for this package. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 5.48.0 | 3 / 9 | |
| 5.47.1 | 3 / 9 | |
| 5.47.0 | 3 / 9 | |
| 5.46.1 | 3 / 9 | |
| 5.46.0 | 3 / 9 | |
| 5.45.1 | 3 / 9 | |
| 5.45.0 | 3 / 9 | |
| 5.44.0 | 3 / 9 | |
| 5.43.0 | 3 / 9 | |
| 5.42.1 | 3 / 9 | |
| 5.42.0 | 3 / 9 | |
| 5.41.1 | 3 / 9 | |
| 5.41.0 | 3 / 9 | |
| 5.40.0 | 3 / 9 | |
| 5.39.0 | 3 / 9 | |
| 5.38.1 | 3 / 9 | |
| 5.37.1 | 3 / 9 | |
| 5.37.0 | 3 / 9 | |
| 5.36.1 | 3 / 9 | |
| 5.36.0 | 3 / 9 | |
| 5.35.0 | 3 / 9 | |
| 5.34.0 | 3 / 9 | |
| 5.33.4 | 3 / 9 | |
| 5.33.3 | 3 / 9 | |
| 5.32.0 | 3 / 9 | |
| 5.31.3 | 3 / 9 | |
| 5.31.2 | 3 / 9 | |
| 5.31.1 | 3 / 9 | |
| 5.31.0 | 3 / 9 | |
| 5.30.1 | 3 / 9 | |
| 5.30.0 | 3 / 9 | |
| 5.29.0 | 3 / 9 | |
| 5.28.0 | 3 / 9 | |
| 5.27.0 | 3 / 9 | |
| 5.26.0 | 3 / 9 | |
| 5.25.0 | 3 / 9 | |
| 5.24.2 | 3 / 9 | |
| 5.24.1 | 3 / 9 | |
| 5.24.0 | 3 / 9 | |
| 5.23.6 | 3 / 9 | |
| 5.23.5 | 3 / 9 | |
| 5.23.4 | 3 / 9 | |
| 5.23.3 | 3 / 9 | |
| 5.23.2 | 3 / 9 | |
| 5.23.1 | 3 / 9 | |
| 5.23.0 | 3 / 9 | |
| 5.22.0 | 3 / 9 | |
| 5.21.0 | 3 / 9 | |
| 5.20.0 | 3 / 9 | |
| 5.19.0 | 3 / 9 | |
| 5.18.1 | 3 / 9 |
v5.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.