spryker/rabbit-mq
The recent work is concentrated in one contributor, and all six workflow actions are unpinned. There is no published security policy, although tests, release notes, and security scanning add useful transparency.
76%
Total Score
67
100
100
50
Health Score Breakdown
All recent commits came from one contributor, creating concentration risk. Organization backing provides some handoff capacity, but no second recent contributor is shown.
Only 2 commits were recorded in the last 3 months, from one active maintainer. Recent releases compensate for some of the low commit volume, but the current source activity is thin.
No repository security policy was found. This is a transparency gap for a package handling message-broker connectivity, though automated security scanning provides partial compensation.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings, but all 6 action references are unpinned. That leaves avoidable build-integrity risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Spryker |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/log Version ^3.7.0 | — | — |
spryker/queue Version ^1.5.0 | — | — |
spryker/store Version ^1.21.0 | — | — |
spryker/guzzle Version ^2.1.0 | — | — |
spryker/kernel Version ^3.76.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 months ago
- Created
- 9 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.