It has no license and no security policy, while the organization owner and usable README provide some context. The package is tiny, but its maintenance capacity remains thin.
42%
Total Score
75
50
50
The package has had no release in more than four years, with zero releases in the last 12 months. Its three-release history shows an early burst but no ongoing maintenance.
The linked repository name does not match the package, and its README does not mention this package. That raises a concrete concern that the repository may not be the package's actual source.
No declared license, license file, or repository license file was detected. That leaves the legal terms for using this dependency unclear.
The linked repository had zero commits and zero active maintainers in the last three months. Although the repository is not archived, current development activity is absent.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance gap rather than a severe risk by itself.
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.