ryanwkell/php-resque-scheduler

Release historydanger

The package has only 3 releases, with no release in more than 6 years and a median interval of about 475 days. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months. Together with the old latest release, this indicates sustained inactivity rather than a brief pause.

Maintainerscaution

Only one registry publishing account is listed. A single publisher is not inherently unsafe, but combined with the inactive repository it provides little evidence of continuing maintenance capacity.

Project backingcaution

The repository is owned by an individual account rather than an organization. That is not a defect by itself, but it provides less visible institutional backing for a package already showing prolonged inactivity.

Repo popularitycaution

The repository has 0 stars, 0 forks, and 1 watcher, offering very little supporting evidence of community adoption or shared maintenance. Popularity is only supporting evidence, so this reinforces rather than establishes the abandonment concern.