aliw1382/telegram-tools
The single-maintainer, user-owned project has little visible adoption and no security policy or scanning. MIT licensing, tests, documentation, and a matching repository improve transparency, but do not offset the maintenance risk.
38%
Total Score
25
100
71
50
Health checks
Only two releases exist, both published about three years ago, with none in the last 12 months. This is strong evidence of an inactive release process for a package intended for ongoing use.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.
One registry maintainer is a meaningful continuity risk for a user-owned project, especially alongside absent recent release and commit activity.
The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these counters provide no supporting evidence of active community use.
Composer build tooling is present, but no security-scanning tools are configured. The missing security automation modestly reduces assurance for a package that handles bot credentials and network requests.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Ali Shahmohammadi |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.2 | — | — |
illuminate/support Version ~5.8.0|^6.0|^7.0|^8.0|^9.0|^10.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 3 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.