The project has five active contributors and six recent commits, with tests, release notes, and a matching repository. Its documented proprietary license is clear, while missing security scanning and two unpinned workflow actions leave minor hygiene concerns.
86%
Total Score
100
100
93
83
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a minor repository hygiene gap, not evidence that the release is unsafe by itself.
The repository has no security policy, leaving vulnerability-reporting expectations and response guidance undocumented. This is a transparency gap, although active project backing partly reduces abandonment concern.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings; two of four action references are unpinned, which is a minor reproducibility gap rather than a severe workflow risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.33.0 | — | — |
spryker/merchant Version ^3.0.0 | — | — |
spryker/data-import Version ^1.3.0 | — | — |
spryker/weekday-schedule Version ^1.0.0 | — | — |
spryker/merchant-opening-hours Version ^1.0.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.