← Home

@agenticmail/core

Core SDK for AgenticMail — email, SMS, and phone number access for AI agents

100
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ope-olatunji

Keywords

emailsmsphoneaiagentmailsmtpimapagenticmailai-agentmcpgoogle-voicetext-message

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped package @agenticmail/core is an email SDK, not a typosquat of cors; name similarity is coincidental. ai

Versions (showing 100 of 112)

Version Deps Published
0.9.42 5 / 7
0.9.41 4 / 6
0.9.40 4 / 6
0.9.39 4 / 6
0.9.38 4 / 6
0.9.37 4 / 6
0.9.36 4 / 6
0.9.35 4 / 6
0.9.34 4 / 6
0.9.33 4 / 6
0.9.32 4 / 6
0.9.31 4 / 6
0.9.30 4 / 6
0.9.29 4 / 6
0.9.28 4 / 6
0.9.27 4 / 6
0.9.26 4 / 6
0.9.25 4 / 6
0.9.24 4 / 6
0.9.23 4 / 6
0.9.22 4 / 6
0.9.21 4 / 6
0.9.20 4 / 6
0.9.19 4 / 6
0.9.15 4 / 6
0.9.14 4 / 6
0.9.13 4 / 6
0.9.12 4 / 6
0.9.11 4 / 6
0.9.10 4 / 6
0.9.9 4 / 6
0.9.8 4 / 6
0.9.7 4 / 6
0.9.6 4 / 6
0.9.5 4 / 6
0.9.4 4 / 6
0.9.3 4 / 6
0.9.2 4 / 6
0.9.1 4 / 6
0.9.0 4 / 6
0.7.6 4 / 6
0.7.5 4 / 6
0.7.4 4 / 6
0.7.3 4 / 6
0.7.2 4 / 6
0.7.1 4 / 6
0.7.0 4 / 6
0.6.1 5 / 7
0.6.0 5 / 7
0.5.61 5 / 7
0.5.59 5 / 7
0.5.58 5 / 7
0.5.56 5 / 7
0.5.55 5 / 7
0.5.52 5 / 7
0.5.51 5 / 7
0.5.50 5 / 7
0.5.49 5 / 7
0.5.48 5 / 7
0.5.47 5 / 7
0.5.46 5 / 7
0.5.45 5 / 7
0.5.44 5 / 7
0.5.43 5 / 7
0.5.42 5 / 7
0.5.41 5 / 7
0.5.40 5 / 7
0.5.39 5 / 7
0.5.38 5 / 7
0.5.36 5 / 7
0.5.35 5 / 7
0.5.34 5 / 7
0.5.33 5 / 7
0.5.32 5 / 7
0.5.31 5 / 7
0.5.30 5 / 7
0.5.29 5 / 7
0.5.28 5 / 7
0.5.27 5 / 7
0.5.26 5 / 7
0.5.25 5 / 7
0.5.24 5 / 7
0.5.23 5 / 7
0.5.22 5 / 7
0.5.21 5 / 7
0.5.20 5 / 7
0.5.19 5 / 7
0.5.18 5 / 7
0.5.17 5 / 7
0.5.16 5 / 7
0.5.15 5 / 7
0.5.14 5 / 7
0.5.13 5 / 7
0.5.11 5 / 7
0.5.10 5 / 7
0.5.9 5 / 7
0.5.8 5 / 7
0.5.7 5 / 7
0.5.6 5 / 7
0.5.5 5 / 7
Showing 100 of 112 Next page →

v0.9.42

1 finding
LOW No provenance attestation provenance

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

v0.9.41

1 finding
LOW No provenance attestation provenance

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

v0.9.40

1 finding
LOW No provenance attestation provenance

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

v0.9.39

1 finding
LOW No provenance attestation provenance

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

v0.9.38

1 finding
LOW No provenance attestation provenance

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

v0.9.37

1 finding
LOW No provenance attestation provenance

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

v0.9.36

1 finding
LOW No provenance attestation provenance

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

v0.9.35

1 finding
LOW No provenance attestation provenance

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

v0.9.34

1 finding
LOW No provenance attestation provenance

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

v0.9.33

1 finding
LOW No provenance attestation provenance

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

v0.9.32

1 finding
LOW No provenance attestation provenance

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

v0.9.31

1 finding
LOW No provenance attestation provenance

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

v0.9.30

1 finding
LOW No provenance attestation provenance

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

v0.9.29

1 finding
LOW No provenance attestation provenance

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

v0.9.28

1 finding
LOW No provenance attestation provenance

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

v0.9.27

1 finding
LOW No provenance attestation provenance

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

v0.9.26

1 finding
LOW No provenance attestation provenance

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

v0.9.25

1 finding
LOW No provenance attestation provenance

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

v0.9.24

1 finding
LOW No provenance attestation provenance

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

v0.9.23

1 finding
LOW No provenance attestation provenance

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

v0.9.22

1 finding
LOW No provenance attestation provenance

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

v0.9.21

1 finding
LOW No provenance attestation provenance

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

v0.9.20

1 finding
LOW No provenance attestation provenance

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

v0.9.19

1 finding
LOW No provenance attestation provenance

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

v0.9.15

1 finding
LOW No provenance attestation provenance

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

v0.9.14

1 finding
LOW No provenance attestation provenance

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

v0.9.13

1 finding
LOW No provenance attestation provenance

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

v0.9.12

1 finding
LOW No provenance attestation provenance

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

v0.9.11

1 finding
LOW No provenance attestation provenance

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

v0.9.10

1 finding
LOW No provenance attestation provenance

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

v0.9.9

1 finding
LOW No provenance attestation provenance

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

v0.9.8

1 finding
LOW No provenance attestation provenance

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

v0.9.7

1 finding
LOW No provenance attestation provenance

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

v0.9.6

1 finding
LOW No provenance attestation provenance

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

v0.9.5

1 finding
LOW No provenance attestation provenance

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

v0.9.4

1 finding
LOW No provenance attestation provenance

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

v0.9.3

1 finding
LOW No provenance attestation provenance

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

v0.9.2

1 finding
LOW No provenance attestation provenance

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

v0.9.1

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.7.6

1 finding
LOW No provenance attestation provenance

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

v0.7.5

1 finding
LOW No provenance attestation provenance

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

v0.7.4

1 finding
LOW No provenance attestation provenance

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

v0.7.3

1 finding
LOW No provenance attestation provenance

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

v0.7.2

1 finding
LOW No provenance attestation provenance

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

v0.7.1

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.1

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.61

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.59

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.58

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.56

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.55

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.52

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.51

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.50

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.49

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.48

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.47

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.46

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.45

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.44

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.43

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.42

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.41

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.40

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.39

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.38

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.36

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.35

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.34

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.33

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.32

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.31

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.30

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.29

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.28

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.27

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.26

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.25

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.24

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.23

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.22

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.21

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.20

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.19

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.18

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.17

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.16

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.15

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.14

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.13

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.11

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.10

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.9

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.8

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.7

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.6

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.

v0.5.5

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@agenticmail/core' is 1 edit(s) away from popular package 'cors'.

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.