Thinking about this more I’m of the opinion that showing CI badges is to serve a proxy metric for code quality. All other things being equal, I would trust a project that has CI set up (I’d also check to see what they’re running in CI). Even though the CI doesn’t correspond to the current version, I don’t see that as a problem. In theory, if there’s CI, a released version should have passed all of it, so I think it’s reasonable to assume that’s true.
If you look at these through this lens you really only see issues of scale (really with number of badges), but we aren’t certain those will actually end up being a factor. The whole way crate metadata is presented and the larger issue of presenting “crate quality” conceptually is currently under experimentation, I don’t think there’s any actions to do about this right now. It’s to keep collecting feedback from more people and see what the community finds useful. Currently it seems like you don’t think it’s useful, but that’s fine as it’s not an undue burden to have this functionality, and various other people find it useful. So let’s see where things go. Once we start to run out of UI space I suggest this topic is due for a revisit, until then let’s keep collecting data.
