Check whether a binary version satisfies a semver range
68%
Total Score
caution
Usable with caveats: maintenance is concentrated in one contributor and the package has little release history.
No build attestation or trusted-publisher provenance is reported, leaving publication origin less transparent; this is a supply-chain transparency gap rather than evidence of maliciousness.
One registry maintainer is consistent with a small project, but it provides limited publishing redundancy when considered alongside concentrated repository activity.
The repository is owned by an individual rather than an organization, so the single-contributor maintenance concentration is not offset by visible organizational backing.
The registry shows only one release over 906 days and no releases in the last 12 months, indicating limited release history and weaker evidence of ongoing registry maintenance.
One contributor made all commits in the last three months, creating a concentrated maintenance dependency and increasing abandonment risk if that contributor stops.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
semver Version ^7.6.0 | — | — |
binary-version Version ^7.1.0 | — | — |
semver-truncate Version ^3.0.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.