Risky to adopt: the package has had no release or commit activity for about two years and five months, leaving maintenance uncertain. It is not deprecated or archived and has a clear license, README, matching repository, and release notes, but those positives do not offset the prolonged inactivity.
42%
Total Score
33
69
83
The package has made six releases, but none in the last 12 months; its latest release was about two years and five months ago. This prolonged release gap is a substantial maintenance concern.
The repository recorded zero commits and zero active maintainers in the last three months, while release history also shows no recent releases. The consistent absence of recent work strongly raises abandonment risk.
Only one registry account has publish access. The matching user-owned repository provides some ownership continuity, but a single maintainer leaves limited resilience if that person stops maintaining the project.
The registry namespace and repository owner match, and the project is owned by a user rather than an organization. This supports identity continuity but offers less institutional backing for long-term maintenance.
Composer build tooling is present, but no security scanning tools are configured. This is a transparency and maintenance gap, though it is less significant than the prolonged lack of development activity.
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.