The last registry release was over 11 years ago, and the repository shows no active maintainers or commits in the last three months. Licensing, repository ownership, and documentation are in place, but the maintenance gap leaves future compatibility uncertain.
42%
Total Score
75
81
50
The latest release was published in October 2014, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment risk for a dependency.
The repository recorded 0 commits and 0 active maintainers in the last three months, indicating no current development activity. The repository was pushed more recently than the package release, but that does not show ongoing maintenance.
The repository has 0 stars and 0 forks, with only 1 watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little external evidence of active use or review.
The repository has no security policy, leaving no documented channel or process for handling vulnerability reports. This is a transparency gap, though it is less significant than the package's long inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
icybee/module-sites Version ~2.0 | — | — |
icybee/module-users Version ~2.0 | — | — |
icanboogie/activerecord Version ~2.1 | — | — |
brickrouge/css-class-names Version ~2.0 | — | — |
icanboogie/module-installer Version ~1.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.