peroxovy/laravel-mail-logging
Its tiny source tree and single registry maintainer leave little evidence of review capacity. The MIT license, usable README, matching repository, and release notes provide useful transparency.
52%
Total Score
50
100
75
75
Health checks
Only one account has registry publishing access. Because the repository is user-owned rather than organization-backed, this leaves a thin publishing and continuity base.
The package and repository are owned by the same individual account, with no organization backing shown. That is consistent ownership but provides limited evidence of long-term maintainer capacity.
The package has 7 releases, but all activity was concentrated around January 2025 and there have been no releases in about 20 months. That long gap is a meaningful maintenance concern for a package handling application error logs.
The repository has 0 stars, 0 forks, and 1 watcher. Popularity is only supporting evidence, but these counters provide little external evidence of adoption or community review.
Composer build tooling is present, but no security-scanning tooling is reported. For a package that sends application logs by email, the lack of visible security automation is a genuine hygiene gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 peroxovy |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 monolog/monolog Version ^2.0 || ^3.0 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 1 year 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.