devzone/log-monitor
Usable with caveats: the package is clearly structured, licensed, tested, and backed by an organization, but it is brand new and has no established maintenance history or security policy. Adopt it only if you can accept the limited evidence of long-term support.
62%
Total Score
75
100
88
83
Health checks
All six releases were published within about 15 hours, and the package is less than a day old. This shows active initial publishing but provides no evidence of sustained maintenance or maturity yet.
The repository shows zero commits and zero active maintainers over the last three months, which is concerning for maintenance evidence. Because the package is less than a day old, this primarily reflects the lack of historical observation rather than proven abandonment.
Composer is used as the build tool, but no security scanning tool is configured. The missing scanning is a modest transparency gap, not a severe risk by itself.
The repository has no security policy. For a package that reads application logs and sends them to a monitoring server, documented vulnerability reporting would improve operational transparency.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 DevZone |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 monolog/monolog Version ^2.0 || ^3.0 | — | — |
guzzlehttp/guzzle Version ^6.5.5 || ^7.0.1 | — | — |
laravel/framework Version ^7.0 || ^8.0 || ^9.0 || ^10.0 || ^11.0 | — | — |
Weekly Downloads
Info
- Last Published
- 19 hours ago
- Created
- 1 day 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.