Summary
Togoder Security scanned the npm package reusify@1.1.0 on Oct 6, 2026. An AI review of 6 source files produced 6 low severity findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 6
No suspicious network activity
NPS-41B98D072FD6
No network requests, sockets, or data exfiltration patterns present.
No credential or environment access
NPS-786C8DDA2507
No access to process.env, filesystem credentials, or sensitive paths.
No dynamic code execution
NPS-FF9CE2597C3D
No eval, new Function, vm, or dynamic imports used.
No process spawning
NPS-204F3FB9EE98
No child_process or shell command invocation.
Import of local modules
NPS-B2742D090AB8
The file requires '../' (reusify) and './fib' which are local package modules, not external sources.
Benign top-level code
NPS-28F2CDEA1EE7
Top-level code only runs a benchmark loop for performance measurement and logs timing to console.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| benchmarks/createNoCodeFunction.js | safe | This is a legitimate benchmark script that measures function call overhead using a local fib module, with no malicious patterns detected. |
| benchmarks/fib.js | safe | Cleared by Jev triage; no further analysis needed |
| benchmarks/reuseNoCodeFunction.js | safe | This is a benign benchmark file for the reusify library; no malicious patterns or security concerns were detected. |
| eslint.config.js | safe | No malicious patterns detected |
| reusify.js | safe | Cleared by Jev triage; no further analysis needed |
| test.js | safe | Cleared by Jev triage; no further analysis needed |
Scanned versions of reusify
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 1.1.0 | No issues | 6 | Oct 6, 2026 |
Frequently asked questions
Is reusify safe to use?
Our AI source review of reusify@1.1.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does reusify contain malware?
No malware was identified in reusify@1.1.0 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was reusify checked?
Togoder Security downloaded the published npm package and had an AI model read its 6 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 reusify 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 reusify@1.1.0, cost nothing.