The single-maintainer project has no tests or security scanning, increasing maintenance risk for an API client. An MIT license, matching repository, and release notes provide useful transparency, but do not offset the long inactivity.
46%
Total Score
25
75
75
The package has had only two releases, with none in the last three years and the latest release in January 2023. That long gap materially raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's prolonged release silence.
One registry publishing account indicates a thin maintainer base. The linked repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected. This is a modest process weakness alongside the inactive repository.
The repository is not archived and was last pushed in April 2023, which is better than an explicitly abandoned project but does not compensate for the subsequent inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
str/str Version ^1.1 | — | — |
guzzlehttp/guzzle Version ^7.5 | — | — |
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.