Re:Ask HN: How do you check for malware in OSS packages?
by shoo on Friday May 24, 2019 @08:07PM
(#20006314)
Maybe some ideas here: httpss://www.owasp.org/index.php/Source_Code_Analysis_Tools
At work we use a commercial tool for static analysis. From what I have seen it is rather stupid, it produces a lot of false positive security issues about things like allocating memory (potential resource exhaustion vulnerability...)
You also probably want to pin versions of all dependencies, and store them in a repository that you control access to (a good idea for reproducibility, ignoring security).
Re:Ask HN: How do you check for malware in OSS packages?
by relaunched on Sunday May 26, 2019 @05:17PM
(#20017581)
There are open source tools for CVE checking, which is a good start, there are also commercial alternatives like Whitesource. CSP headers can help. So is only using packages that are actively updated.
Re:Ask HN: How do you check for malware in OSS packages?
by riyakhanna1983 on Friday May 24, 2019 @07:04PM
(#20006054)
What tools have you been using to scan NPM/Python/Ruby/Go packages for malicious dependencies? How do I know if one of the dependencies in my package is not going to steal my NPM credentials, for example?
At work we use a commercial tool for static analysis. From what I have seen it is rather stupid, it produces a lot of false positive security issues about things like allocating memory (potential resource exhaustion vulnerability...)
You also probably want to pin versions of all dependencies, and store them in a repository that you control access to (a good idea for reproducibility, ignoring security).
[0] https://snyk.io