Usable with caveats: the package is actively published and backed by an organization, but it is only 20 days old, has a single active contributor, and lacks tests and security-policy coverage.
68%
Total Score
67
100
75
88
A README is present, but neither the package nor repository includes tests or a changelog. For a newly released SDK this limits evidence of compatibility coverage and release transparency.
The package is only 20 days old with two releases, so its maintenance record is too short to demonstrate long-term reliability, despite a recent release.
All two recent commits came from one contributor, creating a concentrated maintenance dependency. Organization backing partly reduces handoff risk, but no second active contributor is evidenced.
There were two commits in the last three months, including activity within the recent collection window, but the volume is still modest for establishing sustained maintenance.
The repository uses Composer build tooling, which fits the package ecosystem, but it has no security scanning tools. This is a transparency and assurance gap rather than evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/psr7 Version ^1.7 || ^2.0 | — | — |
guzzlehttp/guzzle Version ^7.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.