cl/git

Its clear README, MIT license, and lack of install scripts reduce adoption friction. The small, single-owner project offers little evidence to offset its maintenance concerns.

Latest v2.4.0

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was nearly five years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk despite a history of 10 releases.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was about three years ago. This provides little evidence of active maintenance.

Maintainers

Only one registry publishing maintainer is listed, and the project is backed by an individual rather than an organization. This leaves limited visible continuity if that maintainer stops contributing.

Repo tooling

Composer build tooling is present, but no security scanning tooling was detected. That weakens automated oversight, although it does not by itself indicate an unsafe release.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a package that processes repository access and activity data.