danielsucupirafunceme/laravel-redis-fallback

Maintainerscaution

Only one account has registry publishing access. That is not proof of unsafe publishing, but it leaves limited visible publishing redundancy for a package already showing no recent activity.

Release historycaution

Only two releases were recorded, both by January 2022, with no releases in the following four years. That leaves compatibility and maintenance uncertain for a Laravel dependency.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for years. This materially raises abandonment risk.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these figures provide no external community signal to offset the inactivity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene concern rather than evidence that the package is unsafe.