The package has had no release or repository commit activity for about four years, and the repository has no security policy or scanning tools. Its organization-backed repository, stable version, license, and included tests provide useful context but do not offset the maintenance risk.
42%
Total Score
50
75
50
Version 1.0.0 was the only release, published about four years ago, with no releases in the last 12 months. This is strong evidence of an unmaintained release line.
There were zero commits and zero active maintainers in the last three months, consistent with the roughly four-year gap since the last push. This materially raises abandonment risk.
The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these counters provide little supporting evidence of adoption or review.
Composer build tooling is present, but no security scanning tools were detected. That is a meaningful transparency and maintenance gap, though not evidence that the package is unsafe by itself.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This adds a transparency concern for a package intended to run tests and checks.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.