A simple way to handle exceptions in Laravel
43%
Total Score
unhealthy
Risky: no release or commit activity since November 2017, leaving this Laravel dependency effectively abandoned.
The package has had no release in more than eight years; its four releases were concentrated in 2017, with none in the last 12 months. This is strong evidence of abandonment for a dependency targeting an evolving framework.
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push in November 2017 and indicating effectively stopped maintenance.
Only one registry account can publish releases, which limits publishing redundancy. The organization-backed repository makes a short registry maintainer list normal, so this is only a modest concern.
Composer build tooling is present, but no security scanning tools are configured. This is a hygiene gap rather than proof of unsafe code.
The assessed version v0.0.4 is not a stable major release, which adds maturity risk alongside the long period without releases.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.