Send Laravel exception reports to Telegram and other channels.
67%
Total Score
caution
A brand-new release has no activity history, and both workflow actions are unpinned.
One registry maintainer is consistent with a user-owned project, but it provides limited evidence of continuity if that individual becomes inactive.
The registry namespace and repository are owned by the same individual account, providing consistent ownership context but no organizational backing.
This is the first release and was published 0 days ago, so there is no demonstrated release or maintenance history yet; its very recent publication partly explains the gap.
There were 0 commits and 0 active maintainers in the last 3 months, but the repository and package are only 0 days old, so this is an absence of history rather than evidence of abandonment.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest verification gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^9.0|^10.0|^11.0|^12.0 | — | — |
guzzlehttp/guzzle Version ^7.2 | — | — |
illuminate/console Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/contracts Version ^9.0|^10.0|^11.0|^12.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.