PHP_CodeSniffer rules (sniffs) to enforce WordPress coding conventions
58%
Total Score
caution
Usable with caveats: release activity has stopped and repository commits have been inactive for three months.
The repository recorded zero commits and zero active maintainers in the last three months. This is a direct maintenance concern for a package whose release history is also inactive.
Although the package has 30 releases over about 394 days, it has had no releases in the last 12 months. That indicates the release stream is currently inactive.
The repository has no security policy. That is a transparency gap, though it is less severe because the package is a coding-standard tool rather than a service handling application data.
All four workflows were analyzed successfully and no audit findings or untrusted checkouts were reported; the pull_request_target trigger therefore has no identified sink. However, all 30 action references are unpinned, leaving the build exposed to moving action revisions.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phpcsstandards/phpcsextra Version ^1.4.0 | — | — |
phpcsstandards/phpcsutils Version ^1.1.0 | — | — |
squizlabs/php_codesniffer Version ^3.13.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.