If you want security, use a secure OS. But it's not so easy, often decisions are made not to have the best technical solution, but to fulfill business agreements.
You probably had to compile libsodium and build a shared object. That can take a long time. But the scripts that run when npm installing modules can contain malicious payload, yes.
I always try to find something that runs in web-assembly, but it's better to avoid nodejs altogether if you want high security.
Go is much better for these kind of things overall.
Operationalization is the process of defining a measurement of a phenomenon.
It's often talked about in reference to measuring intangibles, but it also applies to other measurements. Temperature, for example is operationalized by setting the marks on a thermometer and using them to gauge the temperature of an object. Additionally, measuring the infrared radiation and inferring the temperature by way of the Stefan–Boltzmann law as a infrared thermometer does.
Notably, these aren't measuring the velocities of particles constituting an object and averaging their magnitudes which is the formal definition of temperature.
Likewise, the measurement of sex drive must be defined in order to take such measurements. Often, zero care is taken to the conscious decision to operationalize measuring mental states which is a terrible way to do science - may as well use dowsing rods. Or in other words, how can we be sure the thing we think we're measuring is what we're actually measuring?
