The project has had no new release or repository commits for more than 12 years, with no recent issue or pull-request activity. MIT licensing, automated tests, release notes, and no install-time scripts provide useful transparency, but they do not offset the severe abandonment risk.
38%
Total Score
50
50
81
83
The package has only one release, published more than 12 years ago, with no releases in the last 12 months. This is strong evidence of an unmaintained dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the last release and indicating severe abandonment risk.
The package declares 11 runtime dependencies, including framework and application integrations. This is a meaningful maintenance surface for a package whose last release is more than 12 years old.
Four issues remain open, while there were no new or closed issues and no pull-request activity in the last month. This supports the conclusion that maintenance has effectively stopped.
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency gap, especially for an old package with many runtime dependencies.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
anlutro/curl Version dev-master | — | — |
juy/profiler Version * | — | — |
vespakoen/menu Version dev-master | — | — |
way/generators Version * | — | — |
laravel/framework Version 4.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.