@strapi/provider-email-nodemailer
Nodemailer provider for Strapi
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
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 senior Strapi maintainer with 12,955 approved packages and 3230 days on npm. Transition from bassel17 is a legitimate org handoff within the Strapi ecosystem. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by major version jump (v4→v5); this is a coordinated Strapi v5 monorepo release, not suspicious reactivation. | ai |
Versions (showing 68 of 68)
| Version | Deps | Published |
|---|---|---|
| 5.48.0 | 1 / 3 | |
| 5.47.1 | 1 / 3 | |
| 5.47.0 | 1 / 3 | |
| 5.46.1 | 1 / 3 | |
| 5.46.0 | 1 / 3 | |
| 5.45.1 | 1 / 3 | |
| 5.45.0 | 1 / 3 | |
| 5.44.0 | 1 / 3 | |
| 5.43.0 | 1 / 3 | |
| 5.42.1 | 1 / 3 | |
| 5.42.0 | 1 / 3 | |
| 5.41.1 | 1 / 3 | |
| 5.41.0 | 1 / 3 | |
| 5.40.0 | 1 / 3 | |
| 5.39.0 | 1 / 3 | |
| 5.38.1 | 1 / 3 | |
| 5.38.0 | 1 / 3 | |
| 5.37.1 | 2 / 3 | |
| 5.37.0 | 2 / 3 | |
| 5.36.1 | 2 / 3 | |
| 5.36.0 | 2 / 3 | |
| 5.35.0 | 2 / 3 | |
| 5.34.0 | 2 / 3 | |
| 5.33.4 | 2 / 3 | |
| 5.33.3 | 2 / 3 | |
| 5.33.2 | 2 / 3 | |
| 5.33.1 | 2 / 3 | |
| 5.33.0 | 2 / 3 | |
| 5.32.0 | 2 / 3 | |
| 5.31.3 | 2 / 3 | |
| 5.31.2 | 2 / 3 | |
| 5.31.1 | 2 / 3 | |
| 5.31.0 | 2 / 3 | |
| 5.30.1 | 2 / 3 | |
| 5.30.0 | 2 / 3 | |
| 5.29.0 | 2 / 3 | |
| 5.28.0 | 2 / 3 | |
| 5.27.0 | 2 / 3 | |
| 5.26.0 | 2 / 3 | |
| 5.25.0 | 2 / 3 | |
| 5.24.2 | 2 / 3 | |
| 5.24.1 | 2 / 3 | |
| 5.24.0 | 2 / 3 | |
| 5.23.6 | 2 / 3 | |
| 5.23.5 | 2 / 3 | |
| 5.23.4 | 2 / 3 | |
| 5.23.3 | 2 / 3 | |
| 5.23.2 | 2 / 3 | |
| 5.23.1 | 2 / 3 | |
| 5.23.0 | 2 / 3 | |
| 5.22.0 | 2 / 3 | |
| 5.21.0 | 2 / 3 | |
| 5.20.0 | 2 / 3 | |
| 5.19.0 | 2 / 3 | |
| 5.18.1 | 2 / 3 | |
| 5.18.0 | 2 / 3 | |
| 5.17.0 | 2 / 3 | |
| 5.16.1 | 2 / 3 | |
| 5.16.0 | 2 / 3 | |
| 5.15.1 | 2 / 3 | |
| 5.15.0 | 2 / 3 | |
| 5.14.0 | 2 / 3 | |
| 5.13.1 | 2 / 3 | |
| 5.13.0 | 2 / 3 | |
| 5.12.7 | 2 / 3 | |
| 4.26.2 | 2 / 4 | |
| 4.26.1 | 2 / 4 | |
| 4.26.0 | 2 / 4 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v5.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v5.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.3
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.2
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.1
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.30.1
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.30.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.