Healthy and suitable to depend on. It has a long release history with seven releases in the past year, active contributions from five maintainers, and clear organization backing; the main caveats are the missing security policy and undeclared workflow token permissions.
88%
Total Score
100
94
75
Composer build tooling is present, but no repository security-scanning tools were detected. This is a modest transparency and monitoring gap rather than evidence of abandonment.
The repository has no published security policy, leaving vulnerability-reporting and response expectations undocumented.
The single workflow has no top-level token permissions declaration. No write permissions were observed, but explicitly limiting workflow permissions would provide stronger safety assurance.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^4.0.0 || ^5.6.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/locale Version ^3.0.0 || ^4.0.0 | — | — |
spryker/symfony Version ^3.4.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.