A single maintainer, no security policy, and no security scanning reduce confidence in long-term support. The stable release and matching, non-archived repository provide useful continuity, but maintenance has clearly slowed.
62%
Total Score
50
86
75
Only one account has registry publish access. That is a narrow publishing base and increases continuity risk for a package maintained by an individual.
The package has 9 releases since October 2021, but none in the last 12 months; the latest release was about 18 months ago. This indicates slowed maintenance despite a short historical release interval.
The repository recorded zero commits and zero active maintainers during the last 3 months. Combined with the old latest release, this points to a currently inactive project.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy. That leaves vulnerability reporting and response expectations undocumented, which lowers project transparency.
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.