MIT licensing, repository tests, and organization ownership provide useful transparency. The workflow uses two unpinned actions and the repository has no security policy, leaving maintenance hygiene limited.
44%
Total Score
67
100
92
67
The latest release was 5 years 6 months ago, with no releases in the last 12 months. Although the package has 21 releases and a stable 2.2.0 version, the prolonged release gap raises abandonment risk.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and indicating no observed current maintenance.
There were no new or closed issues or pull requests in the last month, while 1 issue and 1 pull request remain open. This provides little evidence of active support.
The linked repository has no security policy. This weakens vulnerability-reporting transparency, though it is a secondary concern compared with the absence of recent releases and commits.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, both analyzed action references are unpinned, which is a mild reproducibility and maintenance hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6|^7 | — | — |
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.