The package has a clear README, tests, a stable version, and a matching organization-owned repository. Its single Composer runtime dependency is focused, with no install scripts or audited workflow risks, though security scanning is absent.
68%
Total Score
75
100
88
83
Only two releases have been published, with none in the last 12 months and a median interval of about 345 days. The latest release is from October 2024, which indicates slow maintenance for a package developers may need to keep compatible.
There were zero commits and zero active maintainers in the last three months. Combined with the long release interval, this weakens confidence that defects or compatibility changes will be addressed promptly.
Composer is used as the build tool, which fits the package ecosystem, but no security-scanning tool was detected. The missing scanner is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. For a small coding-standard package this is a transparency gap, but it is less consequential than it would be for a package handling application data or credentials.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
wp-coding-standards/wpcs Version ^3.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.