The package has a clear README, repository tests, an MIT license, and active recent development. Maintenance is concentrated in one contributor, while workflows use broad write permissions and seven unpinned actions.
66%
Total Score
67
100
88
75
The package and repository are both owned by the same individual account, which supports clear ownership but provides no organizational backing to offset the concentrated maintainer base.
The package is only 37 days old but has 10 releases, showing active publishing while leaving limited evidence of long-term maintenance stability.
All 14 recent commits came from one contributor, leaving maintenance and release knowledge concentrated in a single person. The repository is user-owned rather than organization-owned, so there is no shown organizational handoff buffer.
Composer build tooling is present, but no security scanning tool was detected. That is a modest transparency and hygiene gap rather than evidence of unsafe code.
The repository has no security policy. For a static-analysis stub package this is not severe, but it gives consumers no documented reporting or response process.
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.