Summary
Togoder Security scanned the npm package @nolyfill/is-core-module@1.0.39 on Oct 6, 2026. An AI review of 1 source file 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 |
|---|---|---|
| index.js | safe | This module simply checks whether a given module specifier is a Node.js built-in module, using only the built-in 'module' API and a hardcoded list; no malicious patterns detected. |
Scanned versions of @nolyfill/is-core-module
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 1.0.39 | No issues | 1 | Oct 6, 2026 |
Frequently asked questions
Is @nolyfill/is-core-module safe to use?
Our AI source review of @nolyfill/is-core-module@1.0.39 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @nolyfill/is-core-module contain malware?
No malware was identified in @nolyfill/is-core-module@1.0.39 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 @nolyfill/is-core-module 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 @nolyfill/is-core-module 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 @nolyfill/is-core-module@1.0.39, cost nothing.