mxrvx/telegram-bot-auth
The MIT license, README, and release notes improve transparency, while the repository is correctly linked and not archived. No security policy is provided, and both releases appeared within three days with no subsequent commit activity, leaving maintenance uncertain.
52%
Total Score
75
83
75
Health Score Breakdown
The package has only two releases, both in July 2025, with no releases in the following 12 months. That short history and prolonged release gap indicate limited maintenance maturity.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the absence of releases after July 2025. This is the strongest evidence that active maintenance may have stopped.
The repository has no security policy. For a package handling Telegram authentication, that weakens the documented path for reporting and managing security issues.
Version v0.1.1 is below 1.0, so the API and behavior may still change even though the release is not marked as a prerelease. This adds some adoption risk for a dependency.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Vgrish |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 mxrvx/orm Version ^0.1.5 | — | — |
slim/psr7 Version ^1.6.0 | — | — |
slim/slim Version ^4.14.0 | — | — |
ramsey/uuid Version ^4.7.5 | — | — |
ably/ably-php Version ^1.1 | — | — |
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.