The MIT license, clear README, and matching organization repository improve transparency. Composer tooling without security scanning or a security policy leaves fewer safeguards, while the stable major and absent install scripts reduce operational friction.
54%
Total Score
75
83
75
The latest release was nearly two years ago, and there were no releases in the last 12 months. This is a meaningful maintenance concern despite the package having 12 releases overall.
The repository recorded zero commits and zero active maintainers over the last three months. Combined with no releases in the last year, this indicates currently inactive maintenance.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no adoption signal to offset the maintenance concerns.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This weakens transparency for a package handling API credentials.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.2|^7.0 | — | — |
indeximstudio/telegram Version 0.1.* | — | — |
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.