← Home

@strapi/provider-email-mailgun

npm Repository Homepage

Mailgun provider for strapi email plugin

51
Versions
SEE LICENSE IN LICENSE
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

pierreburgyaurelsicokoalexandrebodinconvlynico-strapistrapi.adzouzbaronvoninternetmarc-roig-strapijhoward1994bassel17

Keywords

emailstrapimailgun

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 51 of 66)

View all versions
Version Deps Published
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

v5.47.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.47.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.46.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.46.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.45.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.45.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.43.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.42.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.42.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.41.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.41.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.40.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.39.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.38.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.38.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.37.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.37.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.36.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.36.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.35.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.34.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.33.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.33.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.33.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.33.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.33.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.32.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.31.3

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-12-03) provenance

This version was published by a different npm account than previous versions on 2025-12-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.31.2

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-11-20) provenance

This version was published by a different npm account than previous versions on 2025-11-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.31.1

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-11-19) provenance

This version was published by a different npm account than previous versions on 2025-11-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.31.0

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-11-12) provenance

This version was published by a different npm account than previous versions on 2025-11-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.30.1

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-11-05) provenance

This version was published by a different npm account than previous versions on 2025-11-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.30.0

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-10-30) provenance

This version was published by a different npm account than previous versions on 2025-10-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.26.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.23.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.