thereza/laravel-paystack

Release historydanger

The latest release was published over four years ago, with no releases in the last 12 months. Eight total releases show some history, but the long pause indicates likely abandonment.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the repository's last push being over four years ago. This is strong evidence of abandonment risk.

Project backingcaution

The repository is owned by an individual account rather than an organization. That does not establish poor health by itself, but it provides no visible organizational backing to compensate for inactivity.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is supporting evidence rather than a verdict, but these counts provide no external adoption signal alongside the stale activity.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. The missing scanning is a modest hygiene concern, especially for a package handling payment integration.