Clear licensing, documentation, and a matching source repository improve transparency. The package has no reported security scanning, and its workflow uses four unpinned actions. Its organization backing is reassuring, but the limited release history leaves maintenance uncertain.
58%
Total Score
75
86
50
This is the only release, published about 16 months ago, with no releases in the last 12 months. That leaves ongoing maintenance and compatibility uncertain.
The repository recorded zero commits and zero active maintainers in the last three months, despite being pushed about 12 months ago. This is a concrete sign of limited recent maintenance.
Composer build tooling is present, but no security scanning tools are reported. That weakens repository hygiene evidence without proving the package is unsafe.
The repository has no security policy, so there is no stated process for reporting or handling vulnerabilities. The organization backing provides some context but does not replace that process.
The single workflow was fully analyzed and has no untrusted checkouts, script injection, or high-severity findings, but all four action references are unpinned. The missing top-level permissions block is acceptable on its own.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/store Version ^1.16.1 | — | — |
spryker/kernel Version ^3.75.0 | — | — |
spryker/locale Version ^4.1.0 | — | — |
spryker/search Version ^8.0.0 | — | — |
spryker/util-encoding Version ^2.1.1 | — | — |
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.