chipslays/telegram

Release historydanger

Only three releases exist, with none in the last 12 months; the latest release was published over four years ago. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months, consistent with the release history showing no releases for over four years.

Dependency profilecaution

Seven runtime dependencies, including database, pagination, validation, and another Telegram package, create a relatively broad dependency surface for a 0.0.x library.

Repo package mentioncaution

The repository name does not match the package name, and the collected data does not show the package name in its README. This creates uncertainty about whether the linked repository is the package's actual home.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. This is a maintenance and transparency gap for a package with multiple runtime dependencies.