Tests, release notes, and a broad contributor base add useful confidence for adoption. The repository lacks a security policy, and two of four workflow actions are unpinned, leaving modest maintenance and build-hygiene concerns.
82%
Total Score
100
100
89
50
Composer build tooling is present, but no security-scanning tooling was detected, leaving a modest gap in automated security hygiene.
The repository has no security policy, which makes vulnerability reporting and response expectations less transparent for a package used in application infrastructure.
Version 0.3.1 is not a stable major release, so API stability may be lower than for a 1.x package, although it is not marked as a prerelease and recent versions have been released consistently.
The sole workflow was fully analyzed with no injection or high-severity findings and no broad write permissions; however, two of four action references are unpinned, so build reproducibility and action integrity have a minor hygiene concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^5.8.0 | — | — |
spryker/log Version ^3.20.0 | — | — |
spryker/kernel Version ^3.84.0 | — | — |
spryker/symfony Version ^3.15.0 | — | — |
spryker/transfer Version ^3.27.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.