Check whether an IP(v4 or v6) is in an CIDR range
78%
Total Score
healthy
Healthy: recent maintenance and a matching, active repository outweigh the unusually slow release cadence.
No build attestation or trusted-publisher configuration is present, reducing publication transparency. The simple artifact and clean repository evidence partly limit the concern.
The package is over 11 years old and has only four releases, with a median interval of about 2 years and 10 months. A release in the last month and active repository commits partly compensate for the slow cadence.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a transparency gap, though the small package scope limits its practical weight.
Version 0.2.1 is not a prerelease, but the 0.x major version signals that API stability may be less established than for a mature 1.x release.
The workflow audit completed cleanly with no untrusted checkouts, injection findings, or excessive permissions, but both action references are unpinned. That leaves avoidable workflow supply-chain exposure.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-770647 ip-range-check is vulnerable to Server-Side Request Forgery (SSRF) in versions 0.0.1 - 0.2.0. | 0.0.1 - 0.2.0 | Medium |
| Dependency | Last Release | Score |
|---|---|---|
ipaddr.js Version ^2.5.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.