spryker/message-broker
Healthy and suitable to use. It has current releases, active work from five contributors, strong package and repository documentation, and no deprecation or archival concerns; security-policy and workflow-permission gaps are the main caveats.
88%
Total Score
100
100
94
80
Health Score Breakdown
Composer build tooling is present, but no security-scanning tooling was detected, leaving a modest process gap for supply-chain assurance.
No repository security policy was found. This does not show unsafe code, but it reduces transparency about vulnerability reporting and response.
The repository's workflow has no top-level token-permission declaration. No write permissions were observed, but explicitly limiting permissions would provide stronger workflow hygiene.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/log Version ^3.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/monolog Version ^2.0.0 | — | — |
spryker/symfony Version ^3.10.0 | — | — |
spryker/transfer Version ^3.25.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 days ago
- Created
- 4 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.