The library offers no consumer README and no security policy, making integration and risk review harder. Its dependency surface is minimal, and the exact version has published release notes.
52%
Total Score
50
100
71
83
No license is declared, detected, or included in the package or repository. That creates a material legal and adoption risk for a library dependency.
The package has no README, which makes a library harder to integrate; absent tests and a changelog are not concerns here because tests and changelog belong in the source project, while release notes document this version.
The package has four releases over about 3 years and 9 months, with no releases in the last 12 months and a median interval of about 330 days. This indicates slow maintenance, though not abandonment by itself.
The repository had zero commits and zero active maintainers in the last 3 months. Combined with no recent registry releases, this points to stalled maintenance.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of unsafe code.
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.