Production-grade asynchronous critical log dispatcher for Telegram Bot API with rate limiting, topic routing, and message truncation.
58%
Total Score
33
100
83
83
There were zero commits and zero active maintainers during the past three months, despite the package being only 112 days old. This is the strongest maintenance concern and suggests development may already have stopped.
Only one registry account has publish access. This limits publishing redundancy, though the linked repository is also owned by that same individual, so the result is a modest resilience concern rather than evidence of abandonment by itself.
The registry namespace and repository are owned by the same individual account, providing clear ownership but no organizational backing or maintainer redundancy.
The package is only 112 days old and has released twice, with the latest release about 111 days ago. This is limited history, so long-term maintenance is not yet established.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of any visible adoption provides little external validation for a young package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0|^12.0 | — | — |
monolog/monolog Version ^3.0 | — | — |
illuminate/cache Version ^10.0|^11.0|^12.0 | — | — |
illuminate/queue Version ^10.0|^11.0|^12.0 | — | — |
guzzlehttp/guzzle Version ^7.5 | — | — |
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.