wppunk/wpautoload
Repository tests, release notes, and a clear license improve confidence for consumers. The single-maintainer project has little recent activity and no security scanning, so future fixes are uncertain.
58%
Total Score
50
79
75
Health Score Breakdown
The registry lists one maintainer. Because the linked repository is also owned by that user, this indicates a thin contributor base rather than a registry-access anomaly.
The package has made no releases in the last 12 months, and its latest release was in October 2021. This materially raises maintenance and abandonment concerns.
There were no commits and no active maintainers in the last three months. Combined with the old latest release, this is a meaningful sign that fixes may not arrive promptly.
Composer build tooling is present, but no security scanning tools were detected. That leaves a modest transparency and maintenance gap.
The repository has no security policy, so users have no documented route for reporting vulnerabilities or understanding security handling.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 wppunk |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 composer/composer Version ^2.1 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 5 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.