mucts/laravel-sobot

Release historydanger

This is the only release, published about 6 years ago, with no releases in the last 12 months. That strongly increases abandonment risk for a dependency with no demonstrated maintenance cadence.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months, consistent with a project that has been inactive since its initial release. This is the strongest ongoing-maintenance concern.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no external adoption signal to compensate for the inactivity.

Repo toolingcaution

Composer is used for the build, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence of abandonment on its own.

Security policycaution

The repository has no security policy. This weakens vulnerability-reporting transparency, though it is less significant than the long-term inactivity.