Clear documentation, repository tests, and release notes support adoption. Maintenance is still concentrated in one contributor, while workflow references are entirely unpinned and the project lacks a security policy.
67%
Total Score
50
88
75
One contributor made all recent commits, with a 100% share; because the repository is individually owned, there is no shown organizational handoff capacity to offset that concentration.
Only 2 commits were recorded in the last 3 months, which is sparse for a young package and gives limited evidence of sustained maintenance.
Composer build tooling is present, but no security-scanning tooling was detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, making vulnerability reporting and response expectations less clear for adopters.
v0.4.0 is not a stable major release, so its API may still change; it is not marked as a prerelease, which partly offsets that concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tempest/discovery Version ^3.9 | — | — |
illuminate/contracts Version ^13.2 | — | — |
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.