Unfit to use for a new dependency: the package is deprecated and its source repository is archived, with no commits or releases for nearly four years. It has a clear license, README, tests in the repository, and no install-time scripts, but those strengths do not offset abandonment.
15%
Total Score
0
100
50
67
Packagist marks the entire package as abandoned, with no replacement identified. Package-level deprecation is a severe adoption risk because future fixes and support should not be expected.
The package has 12 releases but none in the last three years and nine months; its latest release was in December 2022. The earlier release cadence shows prior development, but does not compensate for the prolonged gap.
The repository recorded zero commits and zero active maintainers over the last three months. Together with the archived repository and package deprecation, this indicates no current maintenance capacity.
The linked repository is archived and was last pushed in December 2022, confirming that active development has ended. This materially increases abandonment risk for a WordPress integration package.
Composer build tooling is present, but no security scanning tools were detected. This is a secondary hygiene concern, while the repository's archived status remains the decisive issue.
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.