imapflow No license 35 versions

imapflow

npm Repository Homepage

35

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

Verified SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

andris

Keywords

imapemailmail

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:child-process-import	AI (semgrep): child_process used only in types.js, a dev-only TypeScript typings build script, not in runtime library code.	ai	2026/04/27
semgrep	semgrep:base64-decode	AI (semgrep): Base64 decoding in authenticate.js is standard IMAP protocol handling for server challenge/response data, not malicious payload execution. Stable false positive for this package.	ai	2026/04/25
dependencies	unvetted-dep:libmime	AI (dependencies): libmime is a legitimate email MIME handling library from the same Postal Systems ecosystem; expected dependency for an IMAP client.	ai	2026/04/25
dependencies	unvetted-dep:libbase64	AI (dependencies): libbase64 is a legitimate base64 encoding library from the Postal Systems ecosystem; expected dependency for an IMAP client.	ai	2026/04/25
dependencies	unvetted-dep:@zone-eu/mailsplit	AI (dependencies): @zone-eu/mailsplit is a legitimate mail parsing library from the Zone EU / Postal Systems ecosystem; expected dependency for an IMAP client.	ai	2026/04/25

Versions (showing 35 of 236)

Version	Deps	Published
1.0.34	9 / 10	2020-03-25
1.0.33	9 / 10	2020-03-20
1.0.32	9 / 10	2020-03-08
1.0.31	9 / 10	2020-03-06
1.0.30	9 / 10	2020-03-06
1.0.29	9 / 10	2020-03-05
1.0.28	9 / 10	2020-03-04
1.0.27	9 / 10	2020-03-02
1.0.26	9 / 10	2020-02-27
1.0.25	9 / 10	2020-02-27
1.0.24	9 / 10	2020-02-26
1.0.23	9 / 10	2020-02-26
1.0.22	9 / 10	2020-02-25
1.0.21	9 / 10	2020-02-21
1.0.20	9 / 10	2020-02-19
1.0.19	9 / 10	2020-02-19
1.0.18	9 / 10	2020-02-18
1.0.17	9 / 10	2020-02-15
1.0.16	9 / 10	2020-02-15
1.0.15	9 / 10	2020-02-13
1.0.14	9 / 10	2020-02-13
1.0.13	9 / 10	2020-02-12
1.0.12	9 / 10	2020-02-12
1.0.11	9 / 10	2020-02-06
1.0.10	9 / 10	2020-02-02
1.0.9	9 / 10	2020-02-02
1.0.8	9 / 10	2020-02-02
1.0.7	9 / 10	2020-01-31
1.0.6	9 / 10	2020-01-30
1.0.5	9 / 10	2020-01-29
1.0.4	8 / 10	2020-01-29
1.0.3	8 / 10	2020-01-28
1.0.2	8 / 10	2020-01-27
1.0.1	8 / 10	2020-01-14
1.0.0	0 / 7	2019-12-19

v1.0.34

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.

v1.0.33

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.

v1.0.32

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.

v1.0.31

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.

v1.0.30

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.

v1.0.29

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.

v1.0.28

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.

v1.0.27

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.

v1.0.26

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.

v1.0.25

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.

v1.0.24

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.

v1.0.23

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.

v1.0.22

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.

v1.0.21

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.

v1.0.20

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.

v1.0.19

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.

v1.0.18

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.

v1.0.17

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.

v1.0.16

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.

v1.0.15

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.

v1.0.14

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.

v1.0.13

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.

v1.0.12

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.

v1.0.11

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.

v1.0.10

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.

v1.0.9

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.

v1.0.8

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.

v1.0.7

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.

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

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

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

v1.0.3

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.

v1.0.2

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.

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

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