A thorough README, broad test coverage, and matching MIT licensing support adoption. The small dependency set and organization ownership add useful context, but this beta remains an early project with limited operating history.
60%
Total Score
75
100
79
67
The package is only 118 days old and has two releases, both published within minutes on the same day. This is too little history to demonstrate sustained maintenance, so it lowers confidence and health.
There were zero commits and zero active maintainers in the last three months. Because the project is young and its latest release was also its last push, this is a meaningful maintenance concern rather than proof of abandonment.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a hygiene gap for a library distributed to other projects.
The repository has no security policy. That weakens vulnerability-reporting transparency, although it is not severe enough to make the release unfit by itself.
The assessed release is a beta, and all recent releases are prereleases. That indicates an API or behavior surface that may still change, although it is not evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/semver Version ^3.4 | — | — |
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.