Usable with caveats: the package is clearly licensed, documented, tested in its repository, and publishes release notes, but it has had no commits or releases since January 2026. A single maintainer and limited security workflow hygiene add maintenance risk for a relatively new library.
64%
Total Score
67
100
89
80
The registry has one publishing maintainer. That is consistent with the user-owned repository, but it leaves little visible publishing redundancy if that maintainer becomes unavailable.
Only two releases were published, both on January 5, 2026, with no later registry releases over the following eight months. That is limited evidence of sustained maintenance for a new package.
The repository recorded zero commits and zero active maintainers during the last three months, and its last push was in January 2026. This is the strongest health concern, although the project is still relatively young.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
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.