3 ms·
Users have to come to grips with the possibility that the "free" code they download might be malicious. To mitigate the risk they have these options: 1 - Don'
by pmoriarty 8y ago
Users have to come to grips with the possibility that the "free" code they download might be malicious.
To mitigate the risk they have these options:
1 - Don't use the software.
2 - Audit the software themselves before they use it.
3 - Pay someone to do the auditing for them.
Even if they choose options 2 or 3, there's still a chance the some vulnerability of malware could sneak through (especially if they're getting a binary blob or source code written in a language like C that makes obfuscation easy).
But if they choose to use unaudited software, they're playing with fire and shouldn't be surprised if from time to time they get burnt.
- rapnie 8y agoI wonder if there are projects out there for an option 4: 4) Use an OSS dependency checker tool that reports the risk in your dependency tree 4a) Dependency tool uses a crowdsourced database of audit/review metrics A typical NodeJS project has potentially 1,000's of (transitive) dependencies. Many well-established projects use dependencies versioned e.g. 0.0.1 etc. I guess there are hundreds of similarly unmaintained packages among these. Lacking 4) a small-time developer working on a side-project only has option 1) (or option 0 - Take the risk) as a feasible way to go.
- wstuartcl 8y agoUsers have to come to grips with the possibility that the "free" code they download might be malicious. denial, anger, bargaining, depression and acceptance. ^^^^^