fomvasss/laravel-notification-channel-turbo-sms

Maintainerscaution

Only one account has registry publish access, creating a limited publishing succession path. This is partly offset by the repository's recent release activity, but it remains a maintenance-capacity concern.

Project backingcaution

The registry namespace and repository owner match, providing consistent ownership evidence. The owner is an individual rather than an organization, so the single-maintainer concern is not institutionally backed.

Repo commit activitycaution

No commits were recorded in the last three months and no maintainers were active during that period. This conflicts with the recent release history and raises a moderate concern about ongoing development between releases.

Repo popularitycaution

The repository has 4 stars and 2 forks, showing limited adoption. Popularity is supporting evidence rather than a decisive health measure, and the package has other signs of maintenance.

Repo toolingcaution

The repository uses Composer for builds, but has no security scanning tools. The missing scanning reduces security-process transparency, although it is not evidence that the package is malicious.