Summary
Togoder Security scanned the npm package type-fest@4.41.0 on Oct 6, 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 4 scanned versions of type-fest are flagged high or critical. The latest scanned version, 5.10.0, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 4.41.0 – 5.10.0 | No issues | 2 | >=4.41.0 <=5.10.0 | |
| 3.13.1 | Not scanned | 1 | 3.13.1 | |
| 1.4.0 – 2.19.0 | No issues | 2 | >=1.4.0 <=2.19.0 | |
| 0.4.1 – 0.21.3 | Not scanned | 8 | >=0.4.1 <=0.21.3 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of type-fest
Frequently asked questions
Is type-fest safe to use?
Our AI source review of type-fest@4.41.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does type-fest contain malware?
No malware was identified in type-fest@4.41.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 type-fest 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 type-fest 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 type-fest@4.41.0, cost nothing.