Summary
Togoder Security scanned the npm package to-regex-range@5.0.1 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 | Cleared by Jev triage; no further analysis needed |
Scanned versions of to-regex-range
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 5.0.1 | No issues | 1 | Oct 6, 2026 |
Frequently asked questions
Is to-regex-range safe to use?
Our AI source review of to-regex-range@5.0.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does to-regex-range contain malware?
No malware was identified in to-regex-range@5.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 to-regex-range 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 to-regex-range 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 to-regex-range@5.0.1, cost nothing.