Eight runtime dependencies, install and update hooks, and no security policy or scanning increase maintenance and operational risk. The MIT license, useful documentation, and matching repository provide some transparency but do not offset the package's age.
40%
Total Score
75
50
83
50
The package declares eight runtime dependencies, including framework, mailer, templating, and console components. This creates meaningful upkeep exposure for a package with no recent maintenance evidence.
Composer runs pre-install, post-install, pre-update, and post-update scripts, increasing the amount of package code executed during dependency operations. No provided signal shows these hooks are constrained or independently reviewed.
The last release was in January 2014, with no releases in the past 12 months and only four releases overall. This is strong evidence of abandonment risk, despite the repository remaining available.
The repository had zero commits and zero active maintainers in the past three months. Combined with the old release history, this indicates that maintenance has effectively stopped.
Composer is used as a build tool, which supports reproducible package management, but no security scanning tools are present. That is a transparency and maintenance gap for a package with several runtime dependencies.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twig/twig Version 1.* | — | — |
xiidea/ezrbac Version 1.2.*@dev | — | — |
symfony/console Version 2.4.*@dev | — | — |
ellislab/codeigniter Version 2.1-stable | — | — |
xiidea/ci-base-model Version 2.1.* | — | — |
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.