bretto36/rapyd-laravel

Release historydanger

The latest release was published over 9 years ago, and there were no releases in the last 12 months. That is a substantial abandonment concern, despite the package having 90 historical releases.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months. Combined with the release hiatus, this points to a meaningful risk that defects and compatibility problems will remain unaddressed.

Project backingcaution

The registry namespace and repository are owned by the same individual account, and no organization backing is shown. This is consistent ownership but leaves a limited observable support base.

Repo popularitycaution

The repository has 1 star, 3 forks, and 1 watcher, indicating very limited visible adoption. Popularity is supporting evidence rather than a verdict, but this provides little evidence of a strong support community.

Repo toolingcaution

Composer is used as a build tool, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a modest transparency and maintenance gap.