Healthy and backed by an active organization, with clear packaging and a stable 1.0.0 release. The registry has seen no new release for over four years, but recent repository activity from five contributors reduces abandonment concern; workflow permissions and the missing security policy remain minor caveats.
78%
Total Score
100
100
88
80
Only two releases exist, with no registry release in over four years, which raises a real freshness concern. Recent repository activity provides some compensation, but does not replace a current published release.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a modest transparency and supply-chain hygiene gap, not evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. The organization-backed repository and active maintenance partly reduce the practical concern.
The CI workflow declares no top-level token permissions, so its default permissions are less explicit than preferred. It does not request top-level write access, limiting the severity of this gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.30.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.