The project has tests, a substantial README, a license, and recent activity. Its young history, single-contributor maintenance, absent security scanning, and unpinned workflow actions leave meaningful continuity and build-hygiene concerns.
70%
Total Score
83
100
88
75
The package is young at 59 days, with two releases and a 14-day median interval. This shows initial activity but provides limited evidence of long-term maintenance.
One contributor made all eight commits in the last three months, so the project has no demonstrated maintainer redundancy. Organization backing partly offsets this, but continuity still depends heavily on one person.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a build-hygiene gap rather than evidence of unsafe code.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency concern for an API client handling credentials.
The sole workflow was fully analyzed with no injection or high-severity findings, but both action references are unpinned. The workflow also lacks a top-level permissions block, which is acceptable on its own; unpinned actions remain a mild supply-chain hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/http-message Version ^1.1 || ^2.0 | — | — |
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.