sequentsoft/threadflow-telegram
The source repository includes tests, a changelog, and release notes, while the package has a clear MIT license and no install-time scripts. Its small audience, absent security policy, and unpinned workflow actions leave less assurance around long-term maintenance and build hygiene.
55%
Total Score
50
100
79
67
Health Score Breakdown
There were no commits and no active maintainers in the three months measured, while the last recorded push was about two years ago. This is meaningful evidence of stalled maintenance.
The package has 25 releases, but none in the last 12 months; the latest registry release was about two and a half years ago. This established early activity is outweighed by the prolonged release gap.
The repository has 1 star, 0 forks, and 2 watchers. Low adoption is supporting evidence of limited community validation, but it does not alone make a small package unsafe to use.
The repository has no security policy. For a package that handles Telegram communications, this weakens vulnerability-reporting transparency and maintainer response expectations.
The assessed release is not marked as a prerelease, although the package remains below major version 1. This is a modest maturity limitation rather than a severe stability concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Serhii Litvinchuk |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.3 | — | — |
sequentsoft/threadflow Version ^0.8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 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.