Security & Supply Chain
Every third-party library on a trading host’s classpath runs with the process’s privileges and adds a CVE feed you have to follow. Aeron® 1.54.1 adds none: client, Media Driver, Archive and Cluster resolve to Aeron and Agrona only. This section counts what the alternatives bring, and shows where the count hides from your scanner.
In this section
Section titled “In this section”- 0 vs 382: Third-Party Code in Your Messaging Stack — Third-party runtime dependencies, client and server, for 15 messaging stacks from Aeron® to Kafka, Pulsar and AutoMQ, at their latest stable releases.
What to check before a messaging library reaches production
Section titled “What to check before a messaging library reaches production”| Check | Why | Example |
|---|---|---|
| Runtime closure, not direct dependencies | The transitive tree is what ships | Pulsar broker 5.0.1 → 282 third-party modules |
| Shaded jars | A relocated copy is invisible to POM-based scanners | rocketmq-client-java 5.2.2 declares 0, contains 42 |
| Phone-home modules | Outbound calls from a host that should make none | chronicle-analytics, on unless -Dchronicle.analytics.disable=true |
| Test libraries at compile scope | Test code on the production classpath | RocketMQ ships awaitility and hamcrest |
This site is not affiliated with, endorsed by, or sponsored by Adaptive Financial Consulting Limited or the Aeron project. Aeron is a registered trademark of Adaptive Financial Consulting Limited.
Aeron is a trademark of Adaptive Financial Consulting Limited in the United Kingdom and other countries.