The package has a clear license, release notes, and a repository with recent, well-distributed activity. Its workflow leaves two of four actions unpinned and the repository has no security policy, which are minor transparency and build-hygiene gaps.
86%
Total Score
100
100
94
50
The project uses Composer build tooling, but no security-scanning tools were detected. This is a modest supply-chain hygiene gap, not evidence of abandonment.
No repository security policy was found, reducing transparency for vulnerability reporting, though the active organization-backed project provides some compensating maintenance capacity.
The sole workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. Two of four action references are unpinned, so build reproducibility has a minor hygiene gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^3.0.0 || ^4.0.0 || ^5.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/product Version ^6.0.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/product-alternative 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.