unreal4u/monolog-telegram
The MIT declaration, release notes, and matching repository provide basic transparency. However, the project has had no release or commit activity for nearly 10 years, remains at v0.2, and lacks a README and security policy.
38%
Total Score
33
100
69
83
Health Score Breakdown
The last release was in December 2016, with no releases in the past 12 months and only two releases overall. This long period without published updates is a substantial abandonment concern.
The repository had zero commits and zero active maintainers in the past three months. Combined with the old last push, this strongly indicates that maintenance has stopped.
One registry publishing account is consistent with a small user-owned project, but it provides little redundancy for ongoing maintenance.
The release includes GitHub notes saying it works with the latest Telegram API, which documents this version's change. The missing README is a minor transparency gap for a library, while missing tests and a changelog in the artifact are normal packaging practice.
The repository is owned by the matching individual account rather than an organization, so there is no organizational backing to offset the thin maintenance base.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Camilo Sperberg |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 monolog/monolog Version ~1.17 | — | — |
unreal4u/telegram-api Version ~2.1 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 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.