The repository includes tests, a license, and Composer/Phing build tooling, but has no security policy and little adoption. Its single-maintainer setup and package/repository naming mismatch add uncertainty for a dependency this old.
42%
Total Score
50
100
67
83
The latest release was published on January 6, 2019, over seven years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk, although the package is not registry-deprecated.
There were zero commits and zero active maintainers in the last three months. Combined with the repository's 2019 last-pushed date, this materially increases abandonment risk.
There are no open issues or pull requests and no recent issue or pull-request activity. This is consistent with a quiet, possibly abandoned project, though it could also reflect a small stable package.
The repository name does not match the package name and its README does not mention the package. Although subpackages can use a broader repository, this combination creates uncertainty that the linked source is the intended project.
The repository has one star, zero forks, and one watcher. This low adoption does not prove a problem, but it offers little supporting evidence of maturity or community resilience.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
erebot/api Version ^0.9.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.