Real-time Laravel log monitoring with Telegram alerts
55%
Total Score
caution
Usable with caveats: the project has no commit or maintainer activity in the last three months.
The repository recorded zero commits and zero active maintainers in the last three months, a concrete sign that maintenance may have stopped after the initial release burst.
Only one registry publishing maintainer is listed, leaving little redundancy if that maintainer becomes unavailable; the repository is also user-owned rather than organization-backed.
The package is about 295 days old but has only three releases, all within a very short initial period, providing limited evidence of sustained maintenance.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, which makes vulnerability reporting and response expectations unclear for a package that monitors application logs.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/console Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/support 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.