The organization-backed project has a long release history, recent release notes, and a clear README. Maintenance is concentrated in one release bot, security scanning is absent, and all four workflow actions are unpinned.
78%
Total Score
83
100
94
75
All three recent commits came from one active contributor, the release bot, leaving maintenance capacity concentrated and increasing continuity risk.
Composer is used for builds, but no security scanning tools were detected, leaving a security-process gap in the repository.
The repository has no security policy, reducing transparency about vulnerability reporting and handling.
The single workflow was fully analyzed with no dangerous triggers or audit findings and no top-level write permissions, but all four action references are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/product-relation Version ^3.7.0 | — | — |
spryker/product-relation-gui Version ^2.1.0 | — | — |
spryker/product-relation-storage Version ^2.7.0 | — | — |
spryker-shop/product-relation-widget Version ^1.5.0 | — | — |
spryker/product-relation-data-import Version ^1.2.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.