@strapi/provider-email-amazon-ses
Amazon SES 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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Strapi monorepo package; dormancy reflects release cadence, not account takeover. Publisher has strong track record. | ai | |
| dependencies | unvetted-dep:node-ses | AI (dependencies): node-ses is the canonical Node.js Amazon SES client and is the expected dependency for this Amazon SES email provider package. Its use is appropriate and stable across versions. | ai | |
| phantom-deps | phantom-dep:@strapi/utils | AI (phantom-deps): @strapi/utils is an internal Strapi monorepo package; phantom-dep detection is a false positive for intra-org monorepo dependencies in this package. | ai | |
| provenance | no-provenance | AI (provenance): Strapi packages historically do not include Sigstore provenance; absence is consistent across all versions and not a risk indicator for this package. | 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)
| Version | Deps | Published |
|---|---|---|
| 5.47.1 | 2 / 4 | |
| 5.47.0 | 2 / 4 | |
| 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.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.41.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.41.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.40.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.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.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.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.35.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.34.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.33.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.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.33.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.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.31.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.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.31.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.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.30.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.30.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.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.