zanysoft/laravel-exception-monitor
The MIT license, clear README, and recent releases support adoption. Security documentation and automated security scanning are absent, while maintenance depends heavily on one contributor.
68%
Total Score
67
100
89
50
Health Score Breakdown
The linked repository is owned by a user account rather than an organization, so the single-contributor concentration is not visibly offset by organizational backing.
All 5 recent commits came from one contributor, giving the project a concentrated maintenance base. That creates a real continuity risk for a user-owned repository.
The repository has 1 star, 0 forks, and 1 watcher. Low adoption is supporting caution about community validation, but popularity alone does not outweigh the recent release and commit activity.
Composer is used as the build tool, but no security-scanning tool is configured. The missing scanning lowers project hygiene confidence without independently making the release unsafe to depend on.
The repository has no SECURITY.md or other security policy. That weakens vulnerability-reporting transparency, especially for a package that handles production exception data.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Zany Soft |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^6.0|^7.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 3 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.