Clear documentation, tests, and a changelog reduce adoption friction. Organization ownership offers some handoff capacity, though the project remains early-stage.
66%
Total Score
67
100
86
88
One contributor made all commits during the last three months, creating a concentrated maintenance risk. Organization ownership provides some capacity for handoff, so this is a caution rather than a severe abandonment signal.
Only one commit was recorded in the last three months, indicating limited recent maintenance activity. The short release history partly offsets this, but continuity is still uncertain.
Composer build tooling is present, but no security scanning tool was detected. The missing scanning is a modest transparency and maintenance gap, not evidence of unsafe code.
The repository has no security policy. For an SDK that handles error, logging, and performance data, this weakens the documented path for reporting vulnerabilities.
Version v0.2.2 is not a prerelease, but the package remains below a stable major version. That indicates an evolving API and some maturity risk for adopters.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0|^12.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.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.