MIT licensing, tests, documentation, and release notes provide a solid foundation. The repository remains available and identifiable, but maintenance evidence is dated and security-process coverage is limited.
62%
Total Score
50
86
50
The package has had 6 releases since June 2018, but none in the last 12 months and the latest registry release was over 5 years ago. This materially raises maintenance and abandonment concerns.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, so there is no recent development activity supporting ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a modest supply-chain hygiene gap.
The linked repository has no security policy, which reduces transparency for reporting and handling vulnerabilities, although this is a process gap rather than evidence of an unsafe release.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^3.0.0 | — | — |
spryker/url Version ^3.0.0 | — | — |
spryker/stock Version ^4.0.0 || ^5.0.0 || ^7.0.0 || ^8.0.0 | — | — |
spryker/store Version ^1.1.0 | — | — |
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.