Yes, I can see that being an issue, and is why we avoid dependencies in Alamofire (sometimes to the detriment of the overall community). So perhaps I'm just saying the SSWG should consider incorporating libraries that serve a more basic purpose than "feature" libraries that can have guaranteed versioning and release support. Things like AnyCodable or OrderedDictionary are gaping holes in the overall Swift ecosystem which would be well served by reliable dependencies. So perhaps this is more of a missed opportunity than a disservice. I know Alamofire could use OrderedDictionary and AnyCodable, along with things like a URLEncodedFormEncoder (Vapor's is too tied to Vapor/NIO), TopLevelEncoder/Decoder, an Empty type, and better JSON parsers.
In the long run, I'm not sure this is a scalable approach to building an ecosystem. Apple can't replicate every library needed with their own version, especially when so much of their work can't evolve separately from their platforms. So empowering the community, not just by blessing every dependency, but by building out the tooling need to find high quality dependencies that can form the basis of a reliable ecosystem.