@strapi/plugin-sentry
Send Strapi error events to Sentry
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@strapi/helper-plugin | AI (dependencies): @strapi/helper-plugin is a first-party Strapi internal package from the same monorepo; unvetted status is a pipeline artifact, not a real risk for this org-scoped package. | ai | |
| provenance | no-provenance | AI (provenance): Strapi's monorepo publishing pipeline does not currently attach Sigstore provenance; this is consistent across all @strapi/* packages and not a risk indicator. | ai | |
| dependencies | unvetted-dep:@strapi/design-system | AI (dependencies): First-party Strapi package in the same org scope; unvetted status reflects review queue lag, not a security concern. | ai | |
| dependencies | unvetted-dep:@strapi/icons | AI (dependencies): First-party Strapi package in the same org scope; unvetted status reflects review queue lag, not a security concern. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard Strapi license declaration pattern used across all their packages; not a risk indicator. | ai | |
| phantom-deps | phantom-dep:@strapi/icons | AI (phantom-deps): First-party @strapi org package; phantom dep finding is consistent with compiled plugin output where imports are bundled rather than directly referenced. | ai | |
| phantom-deps | phantom-dep:@strapi/design-system | AI (phantom-deps): First-party @strapi org package; phantom dep finding is consistent with compiled plugin output where imports are bundled rather than directly referenced. | ai |
Versions (showing 96 of 96)
| Version | Deps | Published |
|---|---|---|
| 5.51.0 | 3 / 8 | |
| 5.50.2 | 3 / 8 | |
| 5.50.1 | 3 / 5 | |
| 5.50.0 | 3 / 5 | |
| 5.49.0 | 3 / 5 | |
| 5.48.1 | 3 / 5 | |
| 5.48.0 | 3 / 5 | |
| 5.47.1 | 3 / 5 | |
| 5.47.0 | 3 / 5 | |
| 5.46.1 | 3 / 5 | |
| 5.46.0 | 3 / 5 | |
| 5.45.1 | 3 / 5 | |
| 5.45.0 | 3 / 5 | |
| 5.44.0 | 3 / 5 | |
| 5.43.0 | 3 / 5 | |
| 5.42.1 | 3 / 5 | |
| 5.42.0 | 3 / 5 | |
| 5.41.1 | 3 / 5 | |
| 5.41.0 | 3 / 5 | |
| 5.31.3 | 3 / 5 | |
| 5.31.2 | 3 / 5 | |
| 5.31.1 | 3 / 5 | |
| 5.31.0 | 3 / 5 | |
| 5.30.1 | 3 / 5 | |
| 5.30.0 | 3 / 5 | |
| 5.29.0 | 3 / 5 | |
| 5.28.0 | 3 / 5 | |
| 5.27.0 | 3 / 5 | |
| 5.26.0 | 3 / 5 | |
| 5.25.0 | 3 / 5 | |
| 5.24.2 | 3 / 5 | |
| 5.24.1 | 3 / 5 | |
| 5.24.0 | 3 / 5 | |
| 5.23.6 | 3 / 5 | |
| 5.23.5 | 3 / 5 | |
| 5.23.4 | 3 / 5 | |
| 5.23.3 | 3 / 5 | |
| 5.23.2 | 3 / 5 | |
| 5.23.1 | 3 / 5 | |
| 5.23.0 | 3 / 5 | |
| 5.22.0 | 3 / 5 | |
| 5.21.0 | 3 / 5 | |
| 5.20.0 | 3 / 5 | |
| 5.19.0 | 3 / 5 | |
| 5.18.1 | 3 / 5 | |
| 5.18.0 | 3 / 5 | |
| 5.17.0 | 3 / 5 | |
| 5.16.1 | 3 / 5 | |
| 5.16.0 | 3 / 5 | |
| 5.15.1 | 3 / 5 | |
| 5.15.0 | 3 / 5 | |
| 5.14.0 | 3 / 5 | |
| 5.13.1 | 3 / 5 | |
| 5.13.0 | 3 / 5 | |
| 5.12.7 | 3 / 5 | |
| 5.12.6 | 3 / 5 | |
| 5.12.5 | 3 / 5 | |
| 5.12.4 | 3 / 5 | |
| 5.12.3 | 3 / 5 | |
| 5.12.2 | 3 / 5 | |
| 5.12.1 | 3 / 5 | |
| 5.12.0 | 3 / 5 | |
| 5.11.3 | 3 / 5 | |
| 5.11.2 | 3 / 5 | |
| 5.11.1 | 3 / 5 | |
| 5.11.0 | 3 / 5 | |
| 5.10.4 | 3 / 5 | |
| 5.10.3 | 3 / 5 | |
| 5.10.2 | 3 / 5 | |
| 5.10.1 | 3 / 5 | |
| 5.10.0 | 3 / 5 | |
| 5.9.0 | 3 / 7 | |
| 5.8.1 | 3 / 7 | |
| 5.8.0 | 3 / 7 | |
| 5.7.0 | 3 / 7 | |
| 5.6.0 | 3 / 7 | |
| 5.5.2 | 3 / 7 | |
| 5.5.1 | 3 / 7 | |
| 5.5.0 | 3 / 7 | |
| 5.4.2 | 3 / 7 | |
| 5.4.1 | 3 / 7 | |
| 5.4.0 | 3 / 7 | |
| 5.3.0 | 3 / 7 | |
| 5.2.0 | 3 / 7 | |
| 5.1.1 | 3 / 7 | |
| 5.1.0 | 3 / 7 | |
| 5.0.6 | 3 / 7 | |
| 5.0.5 | 3 / 7 | |
| 5.0.4 | 3 / 7 | |
| 5.0.3 | 3 / 7 | |
| 5.0.2 | 3 / 7 | |
| 5.0.1 | 3 / 7 | |
| 5.0.0 | 3 / 7 | |
| 4.26.2 | 4 / 6 | |
| 4.26.1 | 4 / 6 | |
| 4.26.0 | 4 / 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.
v5.1.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.1.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.0.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.0.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.0.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.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.
v5.0.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.0.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.0.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.
v4.26.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bassel17) than the most recent previously approved version (alexandrebodin) on 2026-01-08, but bassel17 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.