Healthy and suitable to use. It has regular releases, five active contributors, current repository activity, tests, and a matching source repository; the main caveat is limited repository security hygiene.
88%
Total Score
100
100
94
80
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and assurance gap, though it is not evidence of abandonment.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a modest transparency gap for a maintained package.
The only workflow lacks top-level token permissions, so its effective permissions are not explicitly minimized in the repository metadata. No top-level write permissions were detected, limiting the concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^3.0.0 | — | — |
spryker/store Version ^1.7.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/propel Version ^3.47.0 | — | — |
spryker/product Version ^5.5.0 || ^6.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.