The repository has tests, a clear README, a license, and 14 commits in three months. One person makes all recent commits, while workflows use seven unpinned actions and two grant broad write access.
70%
Total Score
50
100
94
75
The repository is owned by an individual rather than an organization, so the single-maintainer and concentrated-activity concerns are not offset by visible organizational backing.
One contributor made all 14 recent commits, creating a concentrated maintenance path without evidence of an active backup contributor.
The repository recorded 14 commits in three months, showing recent maintenance activity. All of that activity comes from one person, so continuity remains dependent on a single maintainer.
Composer build tooling is present, but no security-scanning tooling was detected. For a small stub package this is a modest transparency gap rather than a severe risk.
The repository has no security policy. This weakens the documented process for reporting and handling issues, though the package's static-analysis scope limits the practical impact.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
php-stubs/wordpress-stubs Version ^5.3 || ^6.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.