pfaciana/wp-update-checker
The project has had no release or commit activity for over a year, and only one person publishes it. Its clear README, license, stable release, and matching repository help, but the workflow leaves all nine actions unpinned and no security scanning is configured.
62%
Total Score
67
100
83
75
Health Score Breakdown
One registry publishing account is a limited publishing base, although the linked repository is user-owned and the project shows direct ownership alignment.
The package has made no releases in the last 12 months, despite nine releases since November 2024; this indicates materially slowed maintenance for a dependency that may need compatibility fixes.
The repository had zero commits and zero active maintainers in the last three months, consistent with the extended release gap and raising abandonment risk.
The repository has only 2 stars, 0 forks, and 1 watcher. This is supporting evidence of a small project rather than a health verdict, but it provides little external maintenance signal.
Composer build tooling is present, but no security scanning tools are configured, leaving a transparency and maintenance-hygiene gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Phil Faciana |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 erusev/parsedown Version ^1.7 | — | — |
pfaciana/composer-smart-autoloader Version ^1 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 1 year 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.