Summary
Togoder Security scanned the npm package @types/debug@4.1.13 on Oct 4, 2026. An AI review of 0 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
No per-file summaries were stored for this scan.
Affected version ranges
None of the 2 scanned versions of @types/debug are flagged high or critical. The latest scanned version, 4.1.13, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of @types/debug
Frequently asked questions
Is @types/debug safe to use?
Our AI source review of @types/debug@4.1.13 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @types/debug contain malware?
No malware was identified in @types/debug@4.1.13 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 @types/debug checked?
Togoder Security downloaded the published npm package and had an AI model read its 0 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 @types/debug 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 @types/debug@4.1.13, cost nothing.