Apache Streams historical reliance on third-party open-source SDKs in streams-contrib was useful in getting a lot of APIs integrations built with minimal project code, but as a result the distribution binary contains a lot of maven dependencies that it doesn't really need, most of which wouldn't be activated in any given application.
The superior pattern the community has endorsed is to heavily rely on several powerful dependencies, primarily other Apache projects, and refactor the code base to eliminate un-necessary third-party dependencies.
A key priority should be to enumerate and prioritize removal of most non-Apache maven dependencies, and refactor to get them out of the projects pom hierarchy.