The release is well documented, includes tests and release notes in the project, and has clear organization backing. Its early maturity and limited operational safeguards leave more maintenance risk than an established dependency.
68%
Total Score
67
100
86
75
One contributor made all five commits in the last three months, creating a low bus factor. Organization ownership provides some handoff capacity, but no second active contributor is shown.
Five commits in the last three months show recent work, but all activity came from one maintainer. That concentration leaves maintenance continuity dependent on a single active contributor.
The project uses Composer for builds, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The otherwise clear project documentation does not compensate for that specific operational gap.
Version v0.1.5 is not a stable-major release, so the API may still change. It is not marked as a prerelease, which partly offsets the concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.