stevegrunwell/wp-enforcer
Its last registry release was about nine years ago, with no recent commits and seven open issues. The MIT license, README, and release notes are helpful but do not offset the lack of maintenance.
8%
Total Score
25
50
75
Health Score Breakdown
Packagist marks the entire package as abandoned, with no replacement provided. This is a severe adoption risk because the registry itself signals that it should no longer be depended on.
The latest release was published about nine years ago, and there were no releases in the last 12 months. This strongly indicates abandonment rather than merely a slow release cadence.
The repository had zero commits and zero active maintainers in the last three months. This confirms that current maintenance capacity is absent.
The linked repository is archived and was last pushed about six years ago. Archived source indicates the project is no longer maintained and makes future fixes unlikely.
There were no new or closed issues or pull requests in the last month, while seven issues remain open. Combined with the archived repository, this supports an inactive-project assessment.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Steve Grunwell |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 wp-coding-standards/wpcs Version * | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 10 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.