serverfireteam/rapyd-laravel

Release historydanger

The latest release was published in August 2018, and there have been no releases in over eight years. That long gap is strong evidence of abandonment risk for a framework integration.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old last push, this materially increases abandonment and compatibility risk.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, and three issues remain open. This suggests little current project attention, though it is less decisive than the release and commit history.

Repo popularitycaution

The repository has only 4 stars and 12 forks, providing limited supporting evidence of broad review or community maintenance. Low popularity alone is not disqualifying for a small package.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. This is a modest transparency and maintenance gap rather than a standalone adoption blocker.