m1ke/git-php-lint

The MIT license, clear README, and matching repository make its purpose and terms easy to verify. Its small scope helps, but expect no maintenance or security updates; pinning the exact version is essential because installation modifies Git hooks.

Latest 1.0.2

Packagist

35%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the repository’s last activity being in 2014. This materially increases the chance that compatibility or security issues will remain unresolved.

Lifecycle scripts

The package uses a post-install command and requires a setup script that adds a Git pre-commit hook through a symlink. This is an operational and supply-chain exposure even though the README clearly warns users to pin the version.

Project backing

The repository is owned by an individual user rather than an organization, so the single-person backing offers limited evidence of ongoing maintenance capacity.

Release history

The package has had only two releases, both in July–August 2014, and none in the last 12 months. This long release silence is strong evidence of abandonment risk.

Repo tooling

The project uses Composer, but no security scanning tooling was found. For this small, old shell-script package that is a modest transparency and maintenance gap rather than evidence of unsafe behavior by itself.