It has a clear MIT license, useful documentation, repository tests, and organization backing. Its broad runtime dependency set and missing security policy add smaller maintenance concerns.
55%
Total Score
50
50
75
83
The package has had no releases in the last 12 months, and its latest release was in December 2015 after only four total releases. This is strong evidence of abandonment risk despite the repository remaining available.
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push being in 2017. This materially increases the risk that issues and compatibility problems will remain unresolved.
The package declares 22 runtime dependencies, including framework, database, console, and middleware components. That breadth increases maintenance and compatibility exposure, especially for an old release.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy. For a package that integrates containers, routing, middleware, and many runtime dependencies, the lack of a documented vulnerability-reporting path is a real transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psy/psysh Version ^0.6.1 | — | — |
twig/twig Version ^1.23 | — | — |
relay/relay Version ^1.0 | — | — |
league/route Version 2.0.0-RC1 | — | — |
monolog/monolog Version ^1.17 | — | — |
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.