jms/cg

The repository is still active enough to remain available, has tests, release notes, and a clear license. However, issue and commit activity is currently absent, and the package has not had a registry release for about 10 years.

Latest 1.2.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest registry release was in August 2016, about 10 years ago, with no releases in the last 12 months. This is a substantial maintenance concern despite the package having a long history.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. Combined with the old registry release, this points to limited current maintenance capacity.

Project backing

The repository is owned by an individual rather than an organization, so the small registry maintainer list is consistent with the observed project backing. It offers limited evidence of institutional maintenance capacity.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while 10 issues and 10 pull requests remain open. This supports the concern that maintenance is currently inactive.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap, not evidence that the package is unsafe by itself.