Exactly this.
If it doesn't meet your standards, don't use it.
Alternatively, go fork yourself.
If it doesn't meet your standards, don't use it.
Alternatively, go fork yourself.
It would be nice to have cargo/rustc support 'allow_unsafe' per module and also for dependencies, so you know you have to review a dependency really well.
>Alternatively, go fork yourself.
I think this could be the new template for Open Source Author to include in their OS work description should they choose to.
Or you get drama like ffmpeg vs libav/avconv.