← Home

@vendure/email-plugin

The `EmailPlugin` generates and sends emails based on Vendure server events.

47
Versions
GPL-3.0-or-later
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

michaelbromleyvendure_teamdlhckhousein_is_programming

Accepted risks

Findings the reviewer chose to accept rather than block on.

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

Version Deps Published
3.7.1 7 / 8
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
3.2.3 7 / 8
3.2.2 7 / 8
3.2.1 7 / 8
3.2.0 7 / 8
3.1.8 7 / 8
3.1.7 7 / 8
3.1.6 7 / 8
3.1.5 7 / 8
3.1.4 7 / 8
3.1.3 7 / 8
3.1.2 7 / 8
3.1.1 7 / 8
3.1.0 7 / 8
3.0.8 7 / 8
3.0.7 7 / 8
3.0.6 7 / 8
3.0.5 7 / 8
3.0.4 7 / 8
3.0.3 7 / 8
3.0.2 7 / 8
3.0.1 7 / 8
3.0.0 7 / 8
2.3.4 7 / 8

v3.7.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.2.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.2.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.2.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.8

1 finding
LOW No provenance attestation provenance

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

v3.1.7

1 finding
LOW No provenance attestation provenance

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

v3.1.6

1 finding
LOW No provenance attestation provenance

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

v3.1.5

1 finding
LOW No provenance attestation provenance

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

v3.1.4

1 finding
LOW No provenance attestation provenance

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

v3.1.3

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.8

1 finding
LOW No provenance attestation provenance

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

v3.0.7

1 finding
LOW No provenance attestation provenance

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

v3.0.6

1 finding
LOW No provenance attestation provenance

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

v3.0.5

1 finding
LOW No provenance attestation provenance

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

v3.0.4

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

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.

v3.0.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.