Clear licensing, repository tests, release notes, and a clean workflow support adoption. Pre-1.0 status and missing security documentation leave some operational uncertainty.
64%
Total Score
50
79
75
The registry namespace and repository are both associated with the same user-owned project. This supports package identity but does not provide organizational maintenance redundancy.
The package is only 41 days old, with four releases and a median interval of about 1 day. This shows active initial publishing but provides limited evidence of sustained maintenance.
One contributor made all 9 recent commits, creating a high single-person dependency for fixes and releases. The repository is user-owned rather than organization-owned, so there is no provided backing signal to offset that concentration.
The repository recorded 9 commits in the last 3 months, showing recent development. Activity is concentrated in one contributor, limiting evidence of broader maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a standalone severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
svix/svix Version ^1.99 | — | — |
illuminate/bus Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/http Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/cache Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/queue Version ^10.0|^11.0|^12.0|^13.0 | — | — |
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.