@strapi/provider-email-sendgrid
Sendgrid provider for strapi email
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 team member with 12,955 approved packages and 3230 days on npm. This is a legitimate internal maintainer transition within the Strapi org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package is part of the Strapi monorepo; dormancy reflects sub-package publish cadence, not project abandonment. Publisher is highly trusted. | ai | |
| phantom-deps | phantom-dep:@strapi/utils | AI (phantom-deps): @strapi/utils is a first-party Strapi monorepo utility; phantom-dep flag is a false positive for this org-scoped package. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard Strapi licensing pattern used consistently across all @strapi/* packages in the monorepo. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 5.47.1 | 2 / 2 | |
| 5.47.0 | 2 / 2 | |
| 5.46.1 | 2 / 2 | |
| 5.46.0 | 2 / 2 | |
| 5.45.1 | 2 / 2 | |
| 5.45.0 | 2 / 2 | |
| 5.44.0 | 2 / 2 | |
| 5.43.0 | 2 / 2 | |
| 5.42.1 | 2 / 2 | |
| 5.42.0 | 2 / 2 | |
| 5.41.1 | 2 / 2 | |
| 5.41.0 | 2 / 2 | |
| 5.40.0 | 2 / 2 | |
| 5.39.0 | 2 / 2 | |
| 5.38.1 | 2 / 2 | |
| 5.38.0 | 2 / 2 | |
| 5.37.1 | 2 / 2 | |
| 5.37.0 | 2 / 2 | |
| 5.36.1 | 2 / 2 | |
| 5.36.0 | 2 / 2 | |
| 5.35.0 | 2 / 2 | |
| 5.34.0 | 2 / 2 | |
| 5.33.4 | 2 / 2 | |
| 5.33.3 | 2 / 2 | |
| 5.33.2 | 2 / 2 | |
| 5.33.1 | 2 / 2 | |
| 5.33.0 | 2 / 2 | |
| 5.32.0 | 2 / 2 | |
| 5.31.3 | 2 / 2 | |
| 5.31.2 | 2 / 2 | |
| 5.31.1 | 2 / 2 | |
| 5.31.0 | 2 / 2 | |
| 5.30.1 | 2 / 2 | |
| 5.30.0 | 2 / 2 | |
| 5.29.0 | 2 / 2 | |
| 5.28.0 | 2 / 2 | |
| 5.27.0 | 2 / 2 | |
| 5.26.0 | 2 / 2 | |
| 5.25.0 | 2 / 2 | |
| 5.24.2 | 2 / 2 | |
| 5.24.1 | 2 / 2 | |
| 5.24.0 | 2 / 2 | |
| 5.23.6 | 2 / 2 | |
| 5.23.5 | 2 / 2 | |
| 5.23.4 | 2 / 2 | |
| 5.23.3 | 2 / 2 | |
| 5.23.2 | 2 / 2 | |
| 5.23.1 | 2 / 2 | |
| 5.23.0 | 2 / 2 | |
| 5.22.0 | 2 / 2 | |
| 5.21.0 | 2 / 2 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. 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.39.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. 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.38.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. 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.38.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-04. 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.37.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. 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.37.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. 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.36.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. 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.36.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-11. 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.35.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. 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.34.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-28. 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.33.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-21. 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.33.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. 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.33.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. 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.33.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-29. 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.33.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-17. 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.32.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. 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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.0
1 findingPackage 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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.