It has a stable major version, clear AGPL licensing, tests, and release notes for this patch. Organization backing and a repository that matches the package add transparency, but the project still looks difficult to rely on for new development.
48%
Total Score
50
78
50
The package has 34 releases since 2013, but none in the last 12 months; its latest release was about 6 years and 6 months ago. This strongly raises abandonment risk despite its historically regular release interval.
The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the old last release, this is strong evidence that maintenance has stopped.
The package declares post-create, post-install, post-update, and pre-update Composer scripts, increasing install-time behavior and review requirements. Their presence alone does not establish a severe problem, but it is a supply-chain hygiene concern.
There are 38 open issues and no new or closed issues or pull requests in the last month, indicating unresolved work alongside ongoing inactivity.
Composer is used as a build tool, providing ordinary project build structure, but no security-scanning tools were detected. That is a modest transparency and maintenance gap for a web framework component.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
tdt/input Version dev-master | — | — |
ml/json-ld Version 1.* | — | — |
doctrine/dbal Version 2.5.12 | — | — |
nesbot/carbon Version ~1.14 | — | — |
phayes/geophp Version dev-master | — | — |
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.