Documentation, licensing, tests, and the matching source repository provide a solid foundation. The project is young, has only one release, and shows no commits in the last three months, so long-term maintenance remains uncertain.
58%
Total Score
50
100
88
88
A single registry maintainer is consistent with an individually owned package, but it provides limited visible publishing redundancy alongside the short release history.
The package has one release over 166 days, with no established release cadence. This is understandable for a young project but leaves maintenance maturity unproven.
There were zero commits and zero active maintainers in the last three months. With only one release, this is a meaningful indication that ongoing maintenance has not yet been demonstrated.
Composer build tooling is present, but no security-scanning tooling was detected. This is a transparency and hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This modestly reduces 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.