stepovenko/laravel-notification-channel-turbosms

Release historydanger

The package has made no release in nearly six years, despite seven releases overall. This is strong evidence of abandonment risk for a Laravel integration package.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the stale release history and indicating no visible ongoing maintenance.

Repo popularitycaution

The repository has zero stars, forks, and watchers, providing no supporting evidence of a broader maintenance or user community. Popularity is only supporting evidence, so this reinforces rather than determines the concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a package handling notification credentials, that is a modest maintenance and transparency gap.

Security policycaution

The repository has no security policy, leaving no documented path for reporting or handling vulnerabilities. This is a transparency gap, though it does not by itself show that the package is unsafe.