Clear README, changelog, and release notes support adoption, while the organization provides useful continuity. The repository lacks a security policy and automated security scanning, so operational transparency is not complete.
86%
Total Score
100
100
94
88
Composer build tooling is present, but no security-scanning tool was detected; this is a modest transparency gap rather than evidence of unsafe code.
The repository has no SECURITY.md or other security policy, leaving vulnerability-reporting expectations unspecified.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^4.0.0 || ^5.0.0 | — | — |
spryker/kernel Version ^3.33.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/merchant Version ^3.0.0 | — | — |
spryker/propel-orm Version ^1.9.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.