@vendure/email-plugin
The `EmailPlugin` generates and sends emails based on Vendure server events.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): vendure_team is the org CI account for the established Vendure project; consistent with normal org maintenance. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped package in established monorepo; description omission is stable pattern. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): Handlebars is a well-known templating library; its use in an email plugin is expected and stable across versions. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Hardcoded placeholder JPEG image literal in dev-mailbox route; not a dynamic or malicious payload. | ai | |
| phantom-deps | phantom-dep:@types/nodemailer | AI (phantom-deps): @types/nodemailer is a type declaration package used by nodemailer; stable false positive for this email plugin. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 3.6.4 | 7 / 8 | |
| 3.6.3 | 7 / 8 | |
| 3.6.2 | 7 / 8 | |
| 3.6.1 | 7 / 8 | |
| 3.6.0 | 7 / 8 | |
| 3.5.7 | 7 / 8 | |
| 3.5.6 | 7 / 8 | |
| 3.5.5 | 7 / 8 | |
| 3.5.4 | 7 / 8 | |
| 3.5.3 | 7 / 8 | |
| 3.5.2 | 7 / 8 | |
| 3.5.1 | 7 / 8 | |
| 3.4.4 | 7 / 8 | |
| 3.4.3 | 7 / 8 | |
| 3.4.1 | 7 / 8 | |
| 3.4.0 | 7 / 8 | |
| 3.3.7 | 7 / 8 | |
| 3.3.6 | 7 / 8 | |
| 3.3.5 | 7 / 8 | |
| 3.3.2 | 7 / 8 | |
| 3.3.1 | 7 / 8 | |
| 3.3.0 | 7 / 8 | |
| 3.2.4 | 7 / 8 | |
| 2.3.4 | 7 / 8 |
v3.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.