nechaienko/laravel-telegram-logging

Release historydanger

The latest release was published more than seven years ago, with no releases in the last 12 months. This is strong evidence of abandonment despite the package having nine historical releases.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observed maintenance capacity.

Maintainerscaution

Only one registry account has publish access. That is a thin publishing base and increases continuity risk, with no organization backing shown to compensate for it.

Repo popularitycaution

The repository has only 2 stars, 0 forks, and 0 watchers. Popularity is not decisive, but these very low adoption signals provide little supporting evidence for ongoing maintenance.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tooling is present. The missing scanning is a modest hygiene gap, especially alongside the absence of recent maintenance.