Summary
Togoder Security scanned the npm package @metamask/safe-event-emitter@3.1.2 on Oct 4, 2026. An AI review of 2 source files produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
Error handling pattern
NPS-A28AAF7E660B
The safeApply function catches errors from event handlers and re-throws them asynchronously via setTimeout. This is an intentional pattern to prevent one listener's exception from interrupting other listeners, commonly used in SafeEventEmitter implementations. It does not execute arbitrary code or perform any malicious actions.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/cjs/index.js | safe | No malicious patterns detected; the file contains a standard SafeEventEmitter implementation with no exfiltration, obfuscation, or suspicious behavior. |
| dist/esm/index.mjs | safe | The code is a benign SafeEventEmitter implementation that adds error isolation to Node's EventEmitter, with no malicious patterns such as data exfiltration, credential harvesting, dynamic code execution, or network/process spawning. |
Affected version ranges
None of the 2 scanned versions of @metamask/safe-event-emitter are flagged high or critical. The latest scanned version, 3.1.3, is not scanned. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 3.1.3 | Not scanned | 1 | 3.1.3 | |
| 2.0.0 – 3.1.2 | No issues | 2 | >=2.0.0 <=3.1.2 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of @metamask/safe-event-emitter
Frequently asked questions
Is @metamask/safe-event-emitter safe to use?
Our AI source review of @metamask/safe-event-emitter@3.1.2 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @metamask/safe-event-emitter contain malware?
No malware was identified in @metamask/safe-event-emitter@3.1.2 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was @metamask/safe-event-emitter checked?
Togoder Security downloaded the published npm package and had an AI model read its 2 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan @metamask/safe-event-emitter together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in @metamask/safe-event-emitter@3.1.2, cost nothing.