The package is clearly documented, licensed, and backed by a matching organization repository with tests and a changelog. Its old registry release history and unpinned workflow actions leave meaningful maintenance and build-reproducibility concerns.
62%
Total Score
75
100
88
75
The latest registry release was over 5 years ago, with no releases in the last 12 months. That is a substantial freshness concern for a dependency, despite the package having a long release history.
There were no commits and no active maintainers in the last 3 months. Combined with no registry releases for over 5 years, this points to limited current maintenance capacity.
The repository uses Composer and Make, showing basic build structure, but it reports no security scanning tools. That is a minor transparency gap rather than a standalone adoption blocker.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
All eight analyzed action references are unpinned, which weakens build reproducibility. The audit found no dangerous triggers, untrusted checkouts, script injection, or top-level write permissions, limiting the severity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
icanboogie/http Version ^4.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.