When I see that a project is written in Rust I assume that beyond the language, their other technology/library/framework choices also tend torwards what is modern and unstable, rather than what is conventional and solid.
That information is relevant to shaping one's view of a project. I think it makes sense to mention that you're using a modern stack.
(Though Rust is already close to moving into the conventional/solid category.)
Beyond your parenthetical, what about Rust is unstable for you today? It would be interesting to me to hear that in order to see if the things that come to mind when hearing that are the same that you meant.
In practical terms and in this case it probably doesn't matter, but that is what people are talking about when they say it's both modern and unstable. It's not entirely unreasonable.
Note that "unstable" doesn't necessarily mean "broken". It just means that the ecosystem is likely to have changed massively looking back at code written today from some theoretical vantage point 5 years in the future.