glooby/task-bundle

Documentation, tests, licensing, and a stable dependency set are in place. The project has not released or committed changes for years, and it has no security policy, so future compatibility and maintenance are uncertain.

Latest 3.0.0

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 18 releases since 2016, but its latest release was in October 2019 and it had no releases in the last 12 months. This is strong evidence of a long-standing maintenance gap.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the old release history, this indicates the project is effectively inactive.

Project backing

The repository is owned by an individual user rather than an organization, and the registry has one maintainer. This is consistent ownership context but provides limited evidence of maintenance capacity.

Repo issue activity

There are six open issues and two open pull requests, but no new or closed issues or pull requests in the last month. This suggests unresolved maintenance demand and little recent engagement.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are present. The missing scanning reduces assurance without making the package unfit by itself.