Tests, release notes, and a matching source repository provide useful transparency. Recent work from five contributors supports continued maintenance, though two of four workflow actions are unpinned and registry releases have stopped.
78%
Total Score
100
100
88
75
The package has had no registry release in the last 12 months, despite a long history and a median release interval of about 201 days. Recent repository commits provide some compensation, but the release gap still lowers confidence in delivery cadence.
Composer build tooling is present, but no security-scanning tool was detected. That is a minor process gap, not evidence of unsafe code by itself.
The repository has no security policy. This reduces transparency around vulnerability reporting, though it is partly offset by the organization-backed project and active maintenance.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.30.0 | — | — |
spryker/product Version ^5.0.0 || ^6.0.0 | — | — |
spryker/propel-orm Version ^1.0.0 | — | — |
spryker/cms-content-widget Version ^1.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.