The release has tests, release notes, a matching organization-owned repository, and no install-time scripts. Its small activity footprint and unpinned workflow references leave maintenance and build-integrity concerns for long-term use.
61%
Total Score
75
100
88
75
The package has 8 releases since August 2018, but none in the last 12 months; its latest release was about 2 years and 5 months ago. This indicates materially slowed maintenance for a dependency.
The repository had zero commits and zero active maintainers in the last 3 months. Combined with the stale registry release history, this raises the risk that fixes and compatibility updates may be delayed.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap, not a severe risk on its own.
The repository has no security policy, leaving no documented process for reporting or handling security issues.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but all 4 of its action references are unpinned. That weakens build reproducibility and update control.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/guzzle Version ^2.3.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
psr/http-client Version ^1.0.0 | — | — |
php-http/httplug Version ^1.0.0 || ^2.0.0 | — | — |
php-http/promise Version ^1.0.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.