The repository has no security policy or security-scanning tools, and its small footprint offers limited maintenance evidence. A clear README, MIT license, organization backing, and no install-time scripts provide useful safeguards, but not enough to offset the age of the release.
38%
Total Score
75
71
75
The latest release was over 7 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite four historical releases.
There were no new or closed issues or pull requests in the measured month. With no current discussion or change activity, this adds to the maintenance concern.
The repository has zero stars and forks and only three watchers. Popularity is not required for a healthy small package, but these figures provide little supporting evidence of active use or review.
Composer build tooling is present, but no security-scanning tooling is reported. That limits evidence of routine security checks for a package with no recent release activity.
No security policy is present in the repository, leaving vulnerability reporting and response expectations undocumented. This is a hygiene and transparency gap, not proof of an unsafe release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.0.0 | — | — |
spryker/zed-request Version ^3.0.0 | — | — |
spryker/setup-frontend Version ^1.0.2 | — | — |
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.