← Home

@types/nodemailer

npm Repository Homepage
11
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): DefinitelyTyped types packages naturally lag upstream; dormancy reflects nodemailer v7 release timing, not account takeover. ai
publish-pattern new-deps-added AI (publish-pattern): @aws-sdk/client-sesv2 is the official AWS SDK; added to support nodemailer v7 SES v2 transport types. ai
source-diff large-new-source-files AI (source-diff): Major version bump (v6→v7) for DefinitelyTyped package; new .d.ts files expected for expanded nodemailer v7 API surface. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types/node is a conventional ambient type dependency for DefinitelyTyped packages; not directly imported by design. ai

Versions (showing 11 of 11)

Version Deps Published
8.0.0 1 / 0
7.0.11 1 / 0
7.0.10 1 / 0
7.0.9 1 / 0
7.0.8 2 / 0
7.0.7 2 / 0
7.0.6 1 / 0
7.0.5 2 / 0
7.0.4 2 / 0
6.4.23 1 / 0
6.4.22 1 / 0

v8.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.

v7.0.11

1 finding
LOW No provenance attestation provenance

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

v7.0.10

1 finding
LOW No provenance attestation provenance

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

v7.0.9

1 finding
LOW No provenance attestation provenance

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

v7.0.8

1 finding
LOW No provenance attestation provenance

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

v7.0.7

1 finding
LOW No provenance attestation provenance

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

v7.0.6

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.

v7.0.5

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.

v7.0.4

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.

v6.4.23

1 finding
LOW No provenance attestation provenance

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

v6.4.22

1 finding
LOW No provenance attestation provenance

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