A small contributor footprint and missing security scanning reduce confidence in ongoing support. The recent release, organization backing, tests, and clear documentation provide useful counterweight; pin this version while checking that maintenance continues.
68%
Total Score
75
100
88
50
The repository had zero commits and zero active maintainers during the last three months. The recent release partly offsets this, but the lack of current development activity lowers maintenance confidence.
The repository has no stars and only three forks, indicating limited visible adoption. Popularity is supporting evidence rather than a verdict, so this is only a modest concern.
Composer build tooling is present, but no security-scanning tool was detected. That leaves a transparency and maintenance-hygiene gap for a package handling authentication and API credentials.
The repository has no security policy. For a package that handles authentication credentials and tokens, this weakens disclosure transparency, although it does not by itself show unsafe code.
The single workflow was fully analyzed with no injection or high-confidence audit findings, but both action references are unpinned. The missing top-level permissions block is acceptable on its own; unpinned actions remain a supply-chain hygiene weakness.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.0|^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.