Its three releases were concentrated in the first month, with no newer release in roughly ten months. MIT licensing, organization backing, a matching repository, and only two runtime dependencies provide a useful baseline.
58%
Total Score
100
100
69
50
A README is present, but it is only 43 characters and provides little consumer guidance. The absence of tests and a changelog in the published artifact is normal packaging practice and is not itself a gap.
The package has only three releases, all within roughly the first month, and the latest release was about ten months ago. That weakens evidence of ongoing maintenance despite the initially regular cadence.
The repository has zero stars, forks, and watchers, providing no external adoption evidence. Popularity is supporting evidence only, so this modestly lowers confidence rather than determining health.
Composer is used as a build tool, but no security-scanning tooling is present. That leaves a meaningful transparency and maintenance-control gap for a security-focused package.
The linked repository is not archived, so it remains available for maintenance. Its last push was about eleven months ago, which is consistent with the stale release history but not an abandonment verdict on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ramsey/uuid Version * | — | — |
guzzlehttp/guzzle Version ^7.9.3 | — | — |
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.