The package includes a clear README, tests, and matching MIT licensing, with an organization-backed repository. Its workflows leave all four actions unpinned and the project lacks security scanning, adding maintenance hygiene concerns.
61%
Total Score
50
64
67
The package has had no release in over two years and none in the last 12 months, despite four releases overall. This is the strongest evidence of stalled maintenance.
There were zero commits and zero active maintainers in the last three months. Combined with the old last release, this indicates the project is currently unattended.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and maintenance-hygiene gap, though not evidence of a defect by itself.
The repository is not archived, but its last push was in May 2024, consistent with the release and commit inactivity. The active status provides only limited reassurance.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a modest transparency gap for a package that handles API credentials and network requests.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.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.