Summary
Togoder Security scanned the npm package d3-timer@3.0.1 on Oct 6, 2026. An AI review of 5 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/d3-timer.js | safe | No malicious patterns detected; this is the legitimate d3-timer library implementing timer utilities without any data exfiltration, credential harvesting, obfuscation, process spawning, or suspicious network or filesystem activity. |
| src/index.js | safe | Cleared by Jev triage; no further analysis needed |
| src/interval.js | safe | Cleared by Jev triage; no further analysis needed |
| src/timeout.js | safe | Cleared by Jev triage; no further analysis needed |
| src/timer.js | safe | Cleared by Jev triage; no further analysis needed |
Frequently asked questions
Is d3-timer safe to use?
Our AI source review of d3-timer@3.0.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does d3-timer contain malware?
No malware was identified in d3-timer@3.0.1 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 d3-timer checked?
Togoder Security downloaded the published npm package and had an AI model read its 5 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 d3-timer 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 d3-timer@3.0.1, cost nothing.