uapixart/laravel-turbosms

Release historydanger

The latest release was published in June 2017, with no releases in the last 12 months, indicating a long period without version maintenance. The seven-release history shows it was once developed, but does not offset the roughly nine-year release gap.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months; its last push was in July 2020. This is strong evidence that ongoing maintenance has stopped, although the repository is not marked archived.

Maintainerscaution

One registry account has publish access. For an individual-owned project this is consistent with the source ownership, but it also indicates a thin maintainer base with little visible redundancy.

Project backingcaution

The package is backed by a matching individual-owned repository rather than an organization, providing direct source visibility but a limited apparent ownership base. That context reinforces the maintenance concern without independently making the package unsafe.

Repo issue activitycaution

There are no open issues or pull requests and no issue or pull-request activity in the last month. While a clean tracker is not inherently negative, combined with zero commits it provides no evidence of active community maintenance.