@strapi/review-workflows
Review workflows for your content
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Strapi monorepo; version gap reflects normal release cadence, not account takeover. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Active Strapi monorepo plugin; new source files across minor versions are expected and consistent with framework growth. | ai | |
| dependencies | unvetted-dep:@strapi/design-system | AI (dependencies): Official Strapi design system package; expected dependency for a Strapi core plugin. | ai | |
| dependencies | unvetted-dep:@strapi/icons | AI (dependencies): Official Strapi first-party package; expected dependency for a Strapi core plugin. | ai | |
| phantom-deps | phantom-dep:react-helmet | AI (phantom-deps): react-helmet is declared as a runtime dependency in package.json; phantom-dep finding is a packaging nuance, not a security issue. | ai | |
| dependencies | unvetted-dep:fractional-indexing | AI (dependencies): Well-known utility library for fractional indexing; no security concerns for this package. | ai | |
| dependencies | unvetted-dep:@strapi/utils | AI (dependencies): Official Strapi first-party utility package; expected dependency for a Strapi core plugin. | ai |
Versions (showing 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 5.51.0 | 15 / 15 | |
| 5.50.2 | 15 / 15 | |
| 5.50.1 | 15 / 10 | |
| 5.50.0 | 11 / 9 | |
| 5.49.0 | 11 / 9 | |
| 5.48.1 | 11 / 9 | |
| 5.48.0 | 11 / 9 | |
| 5.47.1 | 11 / 9 | |
| 5.47.0 | 11 / 9 | |
| 5.46.1 | 11 / 9 | |
| 5.46.0 | 11 / 9 | |
| 5.45.1 | 11 / 9 | |
| 5.45.0 | 11 / 9 | |
| 5.44.0 | 11 / 9 | |
| 5.43.0 | 11 / 9 | |
| 5.42.1 | 11 / 9 | |
| 5.42.0 | 11 / 9 | |
| 5.41.1 | 11 / 9 | |
| 5.41.0 | 11 / 9 | |
| 5.33.0 | 11 / 9 | |
| 5.32.0 | 11 / 9 | |
| 5.31.3 | 11 / 9 | |
| 5.31.2 | 11 / 9 | |
| 5.31.1 | 11 / 9 | |
| 5.31.0 | 11 / 9 | |
| 5.30.1 | 11 / 9 | |
| 5.30.0 | 11 / 9 | |
| 5.29.0 | 11 / 9 | |
| 5.28.0 | 11 / 9 | |
| 5.27.0 | 11 / 9 | |
| 5.26.0 | 11 / 9 | |
| 5.25.0 | 11 / 9 | |
| 5.24.2 | 11 / 9 | |
| 5.24.1 | 11 / 9 | |
| 5.24.0 | 11 / 9 | |
| 5.23.6 | 11 / 9 | |
| 5.23.5 | 11 / 9 | |
| 5.23.4 | 11 / 9 | |
| 5.23.3 | 11 / 9 | |
| 5.23.2 | 11 / 9 | |
| 5.23.1 | 11 / 9 | |
| 5.23.0 | 11 / 9 | |
| 5.22.0 | 11 / 9 | |
| 5.21.0 | 11 / 9 | |
| 5.20.0 | 11 / 9 | |
| 5.19.0 | 11 / 9 | |
| 5.18.1 | 11 / 9 | |
| 5.18.0 | 11 / 9 | |
| 5.17.0 | 11 / 9 | |
| 5.16.1 | 11 / 9 | |
| 5.16.0 | 11 / 9 | |
| 5.15.1 | 11 / 9 | |
| 5.15.0 | 11 / 9 | |
| 5.14.0 | 11 / 9 | |
| 5.13.1 | 11 / 9 | |
| 5.13.0 | 11 / 9 | |
| 5.12.7 | 11 / 9 | |
| 5.12.6 | 11 / 9 | |
| 5.12.5 | 11 / 9 | |
| 5.12.4 | 11 / 9 | |
| 5.12.3 | 11 / 9 | |
| 5.12.2 | 11 / 9 | |
| 5.12.1 | 11 / 9 | |
| 5.12.0 | 11 / 9 | |
| 5.11.3 | 11 / 9 | |
| 5.11.2 | 11 / 9 | |
| 5.11.1 | 11 / 9 | |
| 5.11.0 | 11 / 9 | |
| 5.10.4 | 11 / 9 | |
| 5.10.3 | 11 / 9 | |
| 5.10.2 | 11 / 9 | |
| 5.10.1 | 11 / 10 | |
| 5.10.0 | 11 / 10 | |
| 5.9.0 | 11 / 10 | |
| 5.8.1 | 11 / 10 | |
| 5.8.0 | 11 / 10 | |
| 5.7.0 | 11 / 10 | |
| 5.6.0 | 11 / 10 | |
| 5.5.2 | 11 / 10 | |
| 5.5.1 | 11 / 10 | |
| 5.5.0 | 11 / 11 | |
| 5.4.2 | 11 / 11 | |
| 5.4.1 | 11 / 11 | |
| 5.4.0 | 11 / 11 | |
| 5.3.0 | 11 / 11 | |
| 5.2.0 | 11 / 11 | |
| 5.1.1 | 11 / 11 | |
| 5.1.0 | 11 / 11 | |
| 5.0.6 | 11 / 11 | |
| 5.0.5 | 11 / 11 | |
| 5.0.4 | 11 / 11 | |
| 5.0.3 | 11 / 11 | |
| 5.0.2 | 11 / 11 | |
| 5.0.1 | 11 / 11 | |
| 5.0.0 | 11 / 11 |
v5.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.50.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.