Risky to adopt: the package has seen no release activity for nearly 11 years and no repository commits for nearly 10 years, with 17 open issues still unresolved. It is not deprecated or archived and has a clear license and repository, but the long-standing inactivity makes maintenance and compatibility a serious liability.
38%
Total Score
50
50
75
83
The latest release was published in October 2015, and there have been no releases in the last 12 months. This long release gap is strong evidence of abandonment risk for a package used in a WordPress project.
There were zero commits and zero active maintainers in the last three months, consistent with almost a decade since the last recorded repository push. This is the strongest evidence that bug fixes and compatibility updates are unlikely.
The package declares four runtime dependencies, including PHP and Composer-related tooling. This is not unusually broad, but old dependencies can increase compatibility risk when the package itself has not been updated for years.
Only one registry account has publish access, which is a narrow publishing base. The organization-backed repository provides some continuity, so this is a modest concern rather than a severe one.
The repository has 17 open issues and one open pull request, with no issues or pull requests closed in the last month. Combined with the package's age, this indicates unresolved maintenance demand.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
wcm/git-php-hooks Version ^1 | — | — |
composer/installers Version ~1.0 | — | — |
wcm/git-php-hooks-library Version ^1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.