The MIT declaration, matching repository, substantial README, and release notes improve transparency. No tests or security scanning make future changes harder to validate, while the project shows little evidence of ongoing care.
45%
Total Score
50
50
81
50
Only two releases exist, with none in the last 12 months; the latest release was about three and a half years ago. This is strong evidence of abandonment for an actively maintained framework.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap. The repository is not archived, but that does not compensate for the absence of recent work.
The package declares 14 runtime dependencies and no development dependencies, creating a relatively broad runtime surface for a framework. The signal does not show that any dependency is unsafe, so this is only a modest caution.
A post-create-project-cmd lifecycle script runs during project creation, adding install-time behavior that consumers should understand. It is a modest supply-chain hygiene concern, not a severe risk by itself.
Composer build tooling is present, but no security scanning tools were detected. This weakens ongoing assurance, especially alongside the absence of recent activity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
filp/whoops Version ^2.7 | — | — |
symfony/yaml Version ^4.4 | — | — |
cebe/markdown Version ~1.2.0 | — | — |
cboden/ratchet Version ^0.4.3 | — | — |
symfony/mailer Version ^5.4 | — | — |
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.