The project has had no commits from any maintainer in the last three months, and releases are widely spaced. Its MIT licensing, clear README, repository tests, and changelog provide useful transparency, but the workflow uses two unpinned actions.
61%
Total Score
50
100
88
75
The package has only two releases over 460 days, with a median interval of about 303 days and one release in the last 12 months. This indicates a sparse maintenance cadence, though the latest release is recent enough to avoid an abandonment conclusion.
There were zero commits and zero active maintainers in the last three months. The repository is not archived, but this recent inactivity raises maintenance and abandonment concerns for an SDK.
Composer and Robo are used for project tooling, but no security scanning tool is present. That is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The single workflow was fully analyzed, uses read-only permissions, and has no dangerous sinks or audit findings. However, both of its two action references are unpinned, leaving avoidable build-integrity risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.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.