Healthy and suitable to use, supported by a long release history, a current release, active contributors, and a complete package structure. The repository lacks security scanning and a security policy, and its workflow does not declare top-level permissions.
84%
Total Score
100
100
93
80
Composer build tooling is present, but no security-scanning tool was detected. This is a transparency and assurance gap, though not by itself evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and coordinated disclosure expectations undocumented.
The single CI workflow does not declare top-level token permissions. No top-level write permissions were found, but explicit least-privilege settings would provide stronger workflow hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.48.0 | — | — |
spryker/symfony Version ^3.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.