It has a clear MIT license, tests, README, release notes, and no install-time scripts. Its small dependency surface is straightforward, but adopting it means accepting substantial maintenance and security-policy gaps.
38%
Total Score
25
100
63
75
The package has only one release, published about 9 years ago, with no releases in the last 12 months. That provides strong evidence of abandonment for a library dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's prolonged lack of releases. There is no provided evidence of ongoing maintenance.
Registry publishing access is held by one maintainer, and the project backing identifies a personal account rather than an organization. That leaves limited visible maintenance capacity if the maintainer becomes unavailable.
The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a meaningful transparency gap for a package that accesses breach-related API data.
The latest and only release is v0.1, so the package has never reached a stable major version. This compounds the long period without maintenance and leaves compatibility expectations weak.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.2 | — | — |
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.