The package is clearly documented, tested, and tied to an organization-owned repository, with a stable release and no install-time scripts. Its proprietary license is declared, but absent security scanning and the generated client’s aging dependencies add modest long-term maintenance concerns.
58%
Total Score
75
100
89
83
The package has 14 releases since September 2020, but none in the last 12 months and its latest release was in March 2023. This long release gap is a meaningful maintenance concern.
There were zero commits and zero active maintainers in the last three months, consistent with the long period since the latest release and increasing abandonment risk.
There were no new or closed issues or pull requests in the last month, and no open work is recorded. With no recent commits either, this provides little evidence of active maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a modest repository hygiene gap, not evidence that the package is unsafe.
The repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, though it is less serious for a generated API client than for security-sensitive infrastructure.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.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.