crayoon/gotask

The repository includes tests, a matching source project, an MIT license, and no install-time scripts. Its tiny README, absent security policy, and roughly four years without a release or commit make future fixes and support unlikely.

Latest v2.0.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in about four years: five releases were published in total, with none in the last 12 months. This is strong evidence of abandonment risk despite the stable release history.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the roughly four-year release gap and materially increasing abandonment risk.

Dependency profile

Six runtime dependencies, including PHP, Swoole, Hyperf, and Go-related components, indicate a nontrivial integration surface. The profile is understandable but creates ongoing compatibility maintenance needs for an inactive package.

Package scaffolding

The artifact has a README and the repository has tests and uses GitHub releases, which provide some consumer and maintenance support. The seven-character README is exceptionally thin, limiting practical documentation.

Project backing

The repository owner is an individual user rather than an organization, so the small registry maintainer footprint is not clearly backed by a larger project team. This makes the inactive maintenance pattern more consequential.