Usable with caveats, but this release has not been updated for about seven years and the repository shows no recent activity. Clear package ownership, a matching repository, an MIT declaration, and useful documentation reduce—but do not remove—the abandonment risk.
52%
Total Score
50
67
75
The package has six releases, but none in the last 12 months; its latest release was published about seven years ago. This long period without a release materially increases abandonment risk for a dependency.
The repository recorded no commits and no active maintainers in the last three months, consistent with the package's roughly seven-year release gap. This is the strongest concern despite the repository remaining available.
Only one account has registry publish access, which is a limited operational base. The organization backing makes a short registry maintainer list less concerning, but it does not compensate for the observed lack of recent activity.
The repository uses Composer, giving it basic ecosystem-appropriate build tooling, but it has no reported security scanning tools. This is a modest transparency and maintenance gap rather than a severe risk.
The linked repository is not archived, which means it remains structurally available for maintenance. However, its last push was about seven years ago, so the non-archived status only partly offsets the inactivity 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.