The repository has very little community traction and no security policy, while its workflow dependencies are not pinned. Tests, a clear README, release notes, an organization-owned repository, and a small runtime dependency set provide useful counterweight.
62%
Total Score
83
100
78
67
This package has only one release, published about 13 months ago, with no releases in the past 12 months. That leaves limited evidence of an established maintenance cadence.
There were no commits and no active maintainers in the past three months. Together with the single-release history, this is meaningful evidence of slow ongoing development.
The repository has only 2 stars, no forks, and no watchers. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of broad community support.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy. That makes vulnerability reporting and response expectations less clear for a package intended for application integration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.52.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.