The package has had no release or commit activity for about three years, and only one individual account is listed as its registry maintainer. It remains licensed, non-deprecated, and linked to a matching repository, but the lack of security tooling and policy reduces transparency.
52%
Total Score
67
81
50
One registry account is listed as the maintainer. That is a thin publishing base for continuity, with no organization backing shown to compensate for it.
The latest release was about three years ago, with no releases in the last 12 months; this is a meaningful maintenance concern for a dependency, despite five releases showing some earlier activity.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.
The repository has zero stars and forks and three watchers. Popularity is only supporting evidence, but these values provide little evidence of an active community or broad maintenance support.
Composer build tooling is present, but no security scanning tools are configured. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
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.