Summary
Togoder Security scanned the npm package get-caller-file@2.0.5 on Oct 4, 2026. An AI review of 1 source file produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
stack trace manipulation
NPS-1D6B5500F228
The code temporarily overrides Error.prepareStackTrace to inspect the V8 stack trace for retrieving the caller's filename. While this modifies a built-in object during execution, it is a common and legitimate technique for debugging and introspection, not a malicious pattern. No data is sent externally, no credentials are harvested, and no dynamic code execution occurs.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| index.js | safe | The code is a benign utility for retrieving the caller's file name via V8 stack traces; no malicious patterns detected. |
Frequently asked questions
Is get-caller-file safe to use?
Our AI source review of get-caller-file@2.0.5 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does get-caller-file contain malware?
No malware was identified in get-caller-file@2.0.5 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 get-caller-file checked?
Togoder Security downloaded the published npm package and had an AI model read its 1 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 get-caller-file 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 get-caller-file@2.0.5, cost nothing.