Package Health/rezident/self-documented-telegram-bot-sdk

rezident/self-documented-telegram-bot-sdk

The project has very little adoption and no published security policy. Its focused dependency set, MIT declaration, and lack of install-time scripts reduce exposure but do not offset the maintenance concerns.

Latest 6.6.0

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The last release was published over three years ago, with no releases in the last 12 months. Six total releases show some history, but the long silence is a substantial abandonment concern.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the release gap and indicating a strong risk that maintenance has stopped.

Repo popularity

The repository has one star, no forks, and one watcher, indicating very limited visible adoption. Low popularity is supporting evidence rather than proof of poor quality, but it leaves little external maintenance signal.

Repo tooling

Composer is used for builds, but no security scanning tools were detected. The missing scanning is a hygiene gap for a dependency package, not evidence that the release is unsafe by itself.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency and maintenance concern for a package handling bot credentials and API traffic.