Symfony bundle for Telegram Bot API
68%
Total Score
50
100
100
50
One registry maintainer is consistent with a small user-owned project, but it leaves little publishing redundancy if that maintainer becomes unavailable.
The registry namespace and repository are owned by the same individual account, so ownership is consistent, though it does not provide organizational backing.
No commits or active maintainers were observed in the last three months. The recent release partly offsets this, but the lack of current development activity is a maintenance caution.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
The only workflow was fully analyzed with no high-confidence audit findings or untrusted-trigger sinks, but both action references are unpinned, weakening build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/config Version ^7.0|^8.0 | — | — |
symfony/console Version ^7.0|^8.0 | — | — |
symfony/http-kernel Version ^7.0|^8.0 | — | — |
luzrain/telegram-bot-api Version ^3.11.0 | — | — |
symfony/dependency-injection Version ^7.0|^8.0 | — | — |
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.