Risky to adopt: the last release and repository update were over eight years ago, with no recent commits or active maintainers. The package also lacks a README and any license, although it is not deprecated or archived and has a matching organization-owned repository.
42%
Total Score
50
100
69
75
The latest release was over eight years ago, and there have been no releases in the last 12 months. This strongly suggests abandonment despite the package having four historical releases.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release. No provided activity signal compensates for this maintenance risk.
No declared license or license file was found in the package or repository, leaving the legal terms for reuse unclear.
The package has no README, which makes a small WordPress integration harder for consumers to understand and use. The absence of tests and a changelog is expected for a published artifact, while the GitHub release indicator provides some release documentation evidence.
Composer is used as a build tool, providing basic project structure, but no security scanning tools are present. The limited four-file repository makes the tooling gap less severe than the maintenance and licensing concerns.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version 1.x | — | — |
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.