There have been project that has been forked for these reasons. They never go anywhere because the people forking are not involved in the original community as dev.
As one packaging Go daily for a distro, this doesn't surprise me (though thanks God we are not affected, probably because we unbundle everything and the license for each lib is then verified). Contrary to the Rust ecosystem, there is no central repo location or Cargo.toml that easily allow to parse the licenses used. So no cargo license commands. For static binaries we build, we don't have the entire set of licenses because the chain of dependencies can reach up to 650 packages.
Fedora have been shipping on RISC-V for about three years already. Last I saw, around 95% of packages work. The main exceptions have been thing that need some JIT that hasn't been ported yet -- gcc and llvm have been working for years.
I think it all boil down to manpower. Rust crates need a limited set of compat packages and have a way smaller ecosystem than nodejs. Node developers tend to use as many dependencies they can, resulting in hundreds of deps per app. Rust programs have generally less than 10 direct dependencies, and at worst less than a hundred indirect dependencies, so it is still manageable.
