The package is licensed, tested, and its release notes document concrete changes. Organization backing and a non-archived repository help, but adopting it carries meaningful maintenance and workflow-hygiene risk.
58%
Total Score
75
88
75
Only two releases exist, with the latest published in August 2022 and no releases in the last 12 months. This is a substantial maintenance concern, although the linked repository was pushed more recently.
There were no commits and no active maintainers in the last three months. Combined with the old latest registry release, this indicates a meaningful risk of stalled maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities in an API integration package.
The single workflow was fully analyzed with no injection or high-severity findings, but all 7 action references are unpinned. The missing top-level permissions block is acceptable on its own, while unpinned actions leave avoidable workflow supply-chain exposure.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/guzzle Version ^2.2.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
psr/http-message Version ^1.0.1 | — | — |
spryker/transfer Version ^3.25.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.