@strapi/provider-email-mailgun
Mailgun provider for strapi email plugin
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 core Strapi maintainer with 3230 days of history and 12,955 approved packages; transition from bassel17 is a legitimate org-level maintainer change within Strapi. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by major version transition (v4→v5); v5.30.0 aligns with Strapi's v5 release cycle, not suspicious activity. | ai | |
| dependencies | unvetted-dep:@strapi/utils | AI (dependencies): @strapi/utils is a first-party Strapi dependency, same org scope, expected in all Strapi provider packages. | ai | |
| phantom-deps | phantom-dep:@strapi/utils | AI (phantom-deps): Same org scope; phantom detection is a false positive for intra-monorepo dependencies in Strapi packages. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard Strapi license declaration referencing their LICENSE file; consistent across all Strapi packages. | ai |
Versions (showing 100 of 112)
| Version | Deps | Published |
|---|---|---|
| 5.51.0 | 3 / 5 | |
| 5.50.2 | 3 / 5 | |
| 5.50.1 | 3 / 2 | |
| 5.50.0 | 3 / 2 | |
| 5.49.0 | 3 / 2 | |
| 5.48.1 | 3 / 2 | |
| 5.48.0 | 3 / 2 | |
| 5.47.1 | 3 / 2 | |
| 5.47.0 | 3 / 2 | |
| 5.46.1 | 3 / 2 | |
| 5.46.0 | 3 / 2 | |
| 5.45.1 | 3 / 2 | |
| 5.45.0 | 3 / 2 | |
| 5.44.0 | 3 / 2 | |
| 5.43.0 | 3 / 2 | |
| 5.42.1 | 3 / 2 | |
| 5.42.0 | 3 / 2 | |
| 5.41.1 | 3 / 2 | |
| 5.41.0 | 3 / 2 | |
| 5.40.0 | 3 / 2 | |
| 5.39.0 | 3 / 2 | |
| 5.38.1 | 3 / 2 | |
| 5.38.0 | 3 / 2 | |
| 5.37.1 | 3 / 2 | |
| 5.37.0 | 3 / 2 | |
| 5.36.1 | 3 / 2 | |
| 5.36.0 | 3 / 2 | |
| 5.35.0 | 3 / 2 | |
| 5.34.0 | 3 / 2 | |
| 5.33.4 | 3 / 2 | |
| 5.33.3 | 3 / 2 | |
| 5.33.2 | 3 / 2 | |
| 5.33.1 | 3 / 2 | |
| 5.33.0 | 3 / 2 | |
| 5.32.0 | 3 / 2 | |
| 5.31.3 | 3 / 2 | |
| 5.31.2 | 3 / 2 | |
| 5.31.1 | 3 / 2 | |
| 5.31.0 | 3 / 2 | |
| 5.30.1 | 3 / 2 | |
| 5.30.0 | 3 / 2 | |
| 5.29.0 | 3 / 2 | |
| 5.28.0 | 3 / 2 | |
| 5.27.0 | 3 / 2 | |
| 5.26.0 | 3 / 2 | |
| 5.25.0 | 3 / 2 | |
| 5.24.2 | 3 / 2 | |
| 5.24.1 | 3 / 2 | |
| 5.24.0 | 3 / 2 | |
| 5.23.6 | 3 / 2 | |
| 5.23.5 | 3 / 2 | |
| 5.23.4 | 3 / 2 | |
| 5.23.3 | 3 / 2 | |
| 5.23.2 | 3 / 2 | |
| 5.23.1 | 3 / 2 | |
| 5.23.0 | 3 / 2 | |
| 5.22.0 | 3 / 2 | |
| 5.21.0 | 3 / 2 | |
| 5.20.0 | 3 / 2 | |
| 5.19.0 | 3 / 2 | |
| 5.18.1 | 3 / 2 | |
| 5.18.0 | 3 / 2 | |
| 5.17.0 | 3 / 2 | |
| 5.16.1 | 3 / 2 | |
| 5.16.0 | 3 / 2 | |
| 5.15.1 | 3 / 2 | |
| 5.15.0 | 3 / 2 | |
| 5.14.0 | 3 / 2 | |
| 5.13.1 | 3 / 2 | |
| 5.13.0 | 3 / 2 | |
| 5.12.7 | 3 / 2 | |
| 5.12.6 | 3 / 2 | |
| 5.12.5 | 3 / 2 | |
| 5.12.4 | 3 / 2 | |
| 5.12.3 | 3 / 2 | |
| 5.12.2 | 3 / 2 | |
| 5.12.1 | 3 / 2 | |
| 5.12.0 | 3 / 2 | |
| 5.11.3 | 3 / 2 | |
| 5.11.2 | 3 / 2 | |
| 5.11.1 | 3 / 2 | |
| 5.11.0 | 3 / 2 | |
| 5.10.4 | 3 / 2 | |
| 5.10.3 | 3 / 2 | |
| 5.10.2 | 3 / 2 | |
| 5.10.1 | 3 / 2 | |
| 5.10.0 | 3 / 2 | |
| 5.9.0 | 3 / 3 | |
| 5.8.1 | 3 / 3 | |
| 5.8.0 | 3 / 3 | |
| 5.7.0 | 3 / 3 | |
| 5.6.0 | 3 / 3 | |
| 5.5.2 | 3 / 3 | |
| 5.5.1 | 3 / 3 | |
| 5.5.0 | 3 / 3 | |
| 5.4.2 | 3 / 3 | |
| 5.4.1 | 3 / 3 | |
| 5.4.0 | 3 / 3 | |
| 5.3.0 | 3 / 3 | |
| 5.2.0 | 3 / 3 |
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.