How to detect if a loaded module is a Valkey or a Redis module?

[somechris]

Valkey allows to load both Valkey modules (e.g.: valkey-bloom) and Redis modules (e.g.: redisbloom).

But some modules report the same name in INFO (E.g. valkey-bloom and redisbloom both report as bf. Same for valkey-search and redisearch which both report as search) So it's hard for clients to distinguish between them.

Is there a way to reliably detect which module was loaded?

---

MODULE LIST additionally reports the .so name, but that might get modified along the way.

---

More context:

I'm trying to add Bloom filter support to redis-rs. There, in CI, different versions of Valkey/Redis servers run using different modules. Hence, the tests need to check if a Bloom filter module is present in a supported version or skip. But as valkey-bloom and redisbloom report the same name but obviously use different version numbering, it's tricky to check reliably.

[hamedrabah]

There is no reliable protocol-level discriminator with the fields currently returned by MODULE LIST.

Both implementations can intentionally use the same module name, and the version number only has meaning after the implementation is known. The path is deployment metadata and can be renamed. Valkey's module listing exposes name, version, path, and arguments, but no vendor or origin identifier.

For CI, use the identity of the image/package that started the test server as the source of truth. At runtime, probe capabilities with COMMAND INFO or a harmless feature test and branch on the capability you need, not on an inferred vendor.

If a product truly needs origin detection, the modules need to expose a vendor-specific INFO field or command. Without that addition, any name/version/path heuristic can produce false positives.