The repository is unarchived and includes tests plus a Composer/Phing build. One registry maintainer and no security policy leave limited evidence of ongoing support.
42%
Total Score
50
63
75
The latest release was in May 2018, with no releases in the past 12 months and only two releases across roughly 10 years. This is strong evidence of an aging, likely unmaintained dependency.
There were no commits and no active maintainers in the last three months, consistent with the long gap since the last release. This materially increases maintenance and abandonment risk.
The repository name does not match the package name and its README does not mention the package. Although this could reflect packaging structure, the link provides weak evidence that the repository specifically belongs to this release.
The repository has one star, zero forks, and one watcher. Low adoption is only supporting evidence, but it provides little external evidence of maturity or community support.
The repository uses Composer and Phing for builds, showing basic project automation, but it has no security scanning tools. The missing scanning is a modest hygiene gap rather than a standalone severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
erebot/api Version ^0.9.0 | — | — |
erebot/triggerregistry-module Version ^0.3.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.