esvils/driver-telegram

Release historydanger

The latest release was published in January 2020, with no releases in the last 12 months; the long gap materially raises abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the package's roughly six-year release gap.

Maintainerscaution

Only one registry account has publishing access. That is a thin publishing base for a user-owned project and increases continuity risk, although access records do not prove actual activity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected, providing limited evidence of ongoing security maintenance.

Security policycaution

The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented; the lack of recent activity makes this gap more significant.