Autoload classes following WordPress naming convertions
43%
Total Score
unhealthy
Risky: no release or repository activity since January 2017.
The package has only one release, published about 9 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long gap since its only release. No provided activity signal compensates for this lack of maintenance.
A single registry maintainer is reasonable for an individual-owned project, but it leaves little visible publishing redundancy when combined with the absence of recent releases and commits.
There are no open issues or pull requests, but there is also no recent issue or pull-request activity. This neither demonstrates active support nor adds a separate severe concern.
Composer build tooling is present, which fits the package ecosystem. No security scanning is configured, a minor transparency gap, but this does not outweigh the maintenance evidence.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.