reyhanteam/laravel-telegram-bot-router

Maintainerscaution

Only one registry account has publishing access, which is a limited publishing base; the repository's active commit history provides some compensation but does not remove the continuity risk.

Project backingcaution

The package and repository are owned by the same individual account rather than an organization, so the concentrated maintainer activity represents a genuine single-owner continuity risk.

Release historycaution

The package is only 30 days old but already has 39 releases, with a median interval of about 29 minutes; this shows active development but an unusually rapid cadence that may increase release churn.

Repo bus factorcaution

One contributor made 100% of the 209 commits in the last three months, creating a meaningful single-maintainer continuity risk despite the high activity level.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected; the missing scanner is a transparency gap rather than evidence of unsafe code.