pogo/scheduler

The project has tests, a changelog, release notes, and a matching repository, but recent development has stopped and the release history is still very short. Unpinned workflow actions and broad workflow tokens add maintenance risk.

Latest v0.0.2

Packagist

58%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. For a package with only two releases, this is a meaningful maintenance and abandonment risk.

Dependency profile

Four runtime dependencies include Laravel, Laravel Octane, and PHP CS Fixer. The framework coupling is substantial for a small package, while the collected data provides no development-only dependency separation.

Project backing

The package is published under an organization namespace, but the linked repository is owned by an individual user. The available ownership evidence does not show organizational backing to compensate for the thin maintainer activity.

Release history

Only two releases exist, both within the first few days of publication, with no later release activity over the package's 256-day age. This indicates limited release maturity and raises abandonment concerns.

Repo issue activity

Five pull requests remain open and none were merged in the last month, although one new pull request was opened. This suggests unresolved maintenance work rather than a consistently active review process.