spryker/merchant-relationship-gui
Healthy and suitable to depend on. It has a long release history, a current stable release, active work from five contributors, tests, documentation, and organizational backing. The repository lacks a security policy and explicit workflow token permissions, so review those controls in a security-sensitive environment.
88%
Total Score
100
100
94
75
Health Score Breakdown
Composer build tooling is present, but no security-scanning tools were detected; this is a modest transparency gap, not evidence of abandonment.
The repository has no SECURITY.md or other detected security policy, leaving vulnerability reporting and response expectations less explicit.
The single workflow does not declare top-level token permissions. No top-level write permissions were detected, but the missing explicit restriction leaves workflow privileges less transparent.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/gui Version ^3.45.0 || ^4.0.0 || ^5.6.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/company Version ^1.0.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/merchant Version ^1.1.0 || ^2.3.0 || ^3.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 12 days ago
- Created
- 8 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.