Summary
Togoder Security scanned the npm package @cacheable/memory@2.2.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 | No malicious patterns detected; the code is a legitimate cacheable-memory/keyv LRU cache implementation with no exfiltration, credential harvesting, dynamic execution, or install-time hooks. |
| dist/index.mjs | safe | No malicious patterns detected; the code is a legitimate in-memory caching library with LRU, TTL, statistics, and Keyv adapter functionality, with no data exfiltration, credential harvesting, obfuscation, or suspicious network/process operations. |
Frequently asked questions
Is @cacheable/memory safe to use?
Our AI source review of @cacheable/memory@2.2.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @cacheable/memory contain malware?
No malware was identified in @cacheable/memory@2.2.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/memory 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/memory 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/memory@2.2.0, cost nothing.