Summary
Togoder Security scanned the npm package cacheable@2.5.0 on Oct 6, 2026. An AI review of 2 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/index.cjs | safe | This is the legitimate cacheable library implementing caching with Keyv, hooks, synchronization via Qified, and tag-based invalidation; no malicious patterns such as data exfiltration, credential harvesting, obfuscated code, shell execution, or install-time hooks were detected. |
| dist/index.mjs | safe | No malicious patterns detected; the code is a legitimate caching library with no data exfiltration, credential harvesting, obfuscation, process spawning, or suspicious network/file system activity. |
Frequently asked questions
Is cacheable safe to use?
Our AI source review of cacheable@2.5.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does cacheable contain malware?
No malware was identified in cacheable@2.5.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 cacheable 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 cacheable 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 cacheable@2.5.0, cost nothing.