The Nexcess Coding Standard for PHP_CodeSniffer
68%
Total Score
caution
Usable with caveats: sparse releases and no recent commits limit confidence in ongoing maintenance.
Only two releases exist across about 2 years and 8 months, with one release in the last 12 months and a median interval of about 2 years and 5 months. This is a real maintenance concern, though the latest release is recent.
The repository recorded zero commits and zero active maintainers in the last 3 months. Although it was pushed with the release, the recent inactivity lowers confidence in ongoing maintenance.
Composer is used for builds, but no security scanning tool is reported. That is a transparency and maintenance-hygiene gap, not evidence that the package is unsafe.
The linked repository has no security policy. This weakens vulnerability-reporting transparency, although it does not by itself indicate abandonment.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all three action references are unpinned, leaving a modest workflow supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
automattic/vipwpcs Version ^3.0 | — | — |
slevomat/coding-standard Version ^8.0 | — | — |
squizlabs/php_codesniffer Version ^3.6 | — | — |
phpcompatibility/phpcompatibility-wp Version ^2.1 | — | — |
dealerdirect/phpcodesniffer-composer-installer Version ^1.0 | — | — |
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.