A security policy and automated security scanning are not present, leaving less guidance if problems arise. The release is documented, stable, actively maintained by several contributors, and backed by an organization.
86%
Total Score
100
93
50
The repository uses Composer build tooling, but no security-scanning tools were detected. The missing automated security checks are a modest process gap rather than evidence of abandonment.
No repository security policy was found, so there is no documented path for reporting vulnerabilities or explaining security response practices. This lowers transparency modestly.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^3.45.0 || ^4.0.0 || ^5.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/router Version ^1.12.0 | — | — |
spryker/symfony Version ^3.0.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.