The small, focused artifact has a README, clear licensing, and a matching organization-owned repository. Its dependency set is reasonable for a coding-standard package, but the repository lacks security scanning and a security policy.
60%
Total Score
75
100
64
75
The artifact and repository both contain a license, but the detected GPL-2.0 text is narrower than the manifest's GPL-2.0-or-later declaration, creating a licensing-consistency concern.
The package has only two releases, both published about 92 days ago and within roughly 3 hours of each other, leaving little evidence of an established release cadence.
The repository recorded zero commits and zero active maintainers in the last three months. For a package only 92 days old, this is a meaningful sign that maintenance may have stopped after launch.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap rather than a severe risk.
The linked repository is not archived, although its last push was about 92 days ago, so it remains available but shows limited recent maintenance evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
wp-coding-standards/wpcs Version ^3.3.0 | — | — |
phpcompatibility/phpcompatibility-wp Version ^2.1.8 | — | — |
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.