PHPCS check before commit
52%
Total Score
caution
Usable with caveats: maintenance stopped after February 2021 and the project has limited security oversight.
The latest release was in February 2021, with no releases in the last 12 months, indicating prolonged maintenance inactivity for a package developers may still need to rely on.
There were no commits and no active maintainers in the last three months, consistent with the long release gap and indicating that fixes may not arrive promptly.
Only one registry account has publish access, limiting publishing redundancy, although the repository is owned by an organization, which provides some backing.
The repository uses Composer, but no security-scanning tool was detected. For a hook that executes during developer workflows, this is a meaningful security-process gap, though it does not by itself show unsafe behavior.
The repository has no security policy, leaving no documented path for reporting or handling vulnerabilities in a package that installs and runs Git hooks.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
squizlabs/php_codesniffer Version 3.5.8 | — | — |
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.