The package has a clear README, tests, matching MIT licensing, and release notes for this version. Its small maintainer base, prerelease status, and limited recent commit activity leave less assurance for long-term support.
62%
Total Score
50
100
81
67
No registry release appeared in the last 12 months, and the latest registry release was nearly 3 years ago. The repository was pushed more recently, so this indicates slow registry delivery rather than clear abandonment.
All recent commits came from one contributor, giving the project a very narrow recent contributor base. The matching repository and package context provide some reassurance but do not remove the continuity risk.
Only one commit was recorded in the last 3 months, with one active maintainer. That is limited activity, although it does not by itself show that maintenance has stopped.
Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This matters for a package that integrates into application error handling.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filp/whoops Version ^2.0 | — | — |
cakephp/cakephp Version ^5.0 | — | — |
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.