The MIT license and focused 26-file layout make the package easy to inspect. Its documentation, tests, security scanning, and recent development evidence are limited, so future maintenance is uncertain.
55%
Total Score
50
100
75
75
The package has no README, tests, or changelog. Missing tests and changelog are normal for published Composer artifacts, but a library without a README gives consumers little integration guidance.
This is a young package, 123 days old, with only one release and no established release cadence. That is an early-maturity concern, though it is not evidence of abandonment by itself.
There were zero commits and zero active maintainers in the last three months, with the last push occurring at the initial release. For a package only 123 days old, this leaves maintenance continuity unproven.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are configured. This is a modest repository-hygiene gap rather than a standalone dependency blocker.
The repository has no security policy, reducing transparency about vulnerability reporting and response. The package is small and has no observed workflow exposure, which limits the practical impact of this gap.
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.