The MIT license, matching source repository, and small dependency set improve transparency and keep the package easy to inspect. Composer tooling and Dependabot provide useful project support.
64%
Total Score
75
100
93
50
The repository recorded zero commits and zero active maintainers in the last 3 months. Recent registry releases and a recent repository push partly offset this, but the observed development activity is still quiet.
No security policy was found in the linked repository. This is a transparency gap, although it is less significant for a small API client than for security-sensitive infrastructure.
Version 0.6.1 is not a prerelease, but the project remains below a stable 1.0 major release. That is a maturity caveat, partly offset by its long release history and recent publication.
The single workflow is fully analyzed and has no untrusted checkout or script-injection findings, but it grants top-level write permissions, uses an unpinned action, and has a high-confidence medium-severity secrets-inherit finding. These workflow hygiene and credential-scope issues lower supply-chain transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
rmccue/requests Version ^2.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.