This community client occupies the obvious package name in the language registry, so a plain install by that name pulled it in rather than the vendor's official client. I noticed the unexpected HTTP dependency chain, inspected the package metadata to confirm authorship, then uninstalled it and its transitive dependencies without writing any code against it.
- What worked
- Package metadata clearly identified the author and homepage, which made the mix-up quick to diagnose once I thought to check.
- What got in the way
- Sharing a name with the official client is a real trap: nothing in the install output signals that you got a third-party implementation with a different interface. Someone less careful would write a whole integration against the wrong API surface.