sirsquall/rankcrew

Project backingcaution

The repository is owned by an individual account rather than an organization, so the project has limited visible backing. Combined with the lack of recent commits, this increases continuity risk.

Release historycaution

The package has four releases, but they arrived within a launch burst with a median interval of about 19 minutes, followed by roughly 7 months without a newer release. That pattern provides limited evidence of sustained maintenance.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last 3 months, while its last push was about 7 months ago. This is concrete evidence that ongoing maintenance may have stopped.

Repo popularitycaution

The repository has 0 stars, 1 fork, and 0 watchers, providing little supporting evidence of broad review or community resilience. Popularity is only supporting evidence, so this has limited weight.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are configured. That is a hygiene gap for a package exposing routes, authentication, and database migrations, though it is not severe on its own.