The package has a README, tests, a tiny dependency footprint, and no install-time scripts. Its only registry release was in December 2017, recent commit activity is absent, and the linked repository does not clearly identify this package.
58%
Total Score
75
71
75
The package has only one release, published about 8 years and 9 months ago, with no releases in the last 12 months. This is strong evidence of limited ongoing maintenance, despite the package not being deprecated.
The repository had no commits and no active maintainers in the last three months. That weakens evidence of active maintenance, even though the repository itself is not archived.
The repository name does not match the package name and its README does not mention the package. That makes package-to-source ownership less transparent, although the shared organization backing provides some context.
The project uses Composer, but no security scanning tools were detected. For this small PHP library, the missing scanning automation is a minor transparency gap rather than a severe risk.
The repository has no security policy. This is a modest transparency gap for a dependency, though the package has a small scope and no other provided signal indicates a security incident.
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.