This package in question has no dependencies and I can read the source code, can't do that with a binary.
Though I agree, but for other reasons, this tool is a bit silly in JS because you also need node, and it's basically just moving files around.
Not really as npm and yarn are whole package managers that work in parallel to your distro's standard package manager. They pull various sources (that haven't been vetted by anyone except hopefully by the end programmer who told you to use npm install) from who knows where and install them either in your own home, or system-wide with -g like suggested here.
I would never use npm to install a system tool.
The issue is fragmenting tools between multiple package managers. That's a pain, and the source of my opposition to this concept here. Doubly so if they're language specific package managers (fine for development/in isolation, not for system wide user facing tools though).