> For the complete documentation index, see [llms.txt](https://kb.chrisltd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.chrisltd.com/cheat-sheets/security-tools.md).

# Security Tools

Check your open source dependencies for critical vulnerabilities.

**Yarn**

`$ yarn audit --level critical`

**NPM**

`$ npm audit | grep Critical -B3 -A10`

**Ruby Gems**

`$ gem install bundler-audit`\
`$ bundle audit`

Run all development projects through Docker, a virtual machine, or a remote machine to protect your system and other projects.

### Resources

* [NPM Advisories](https://www.npmjs.com/advisories)
* [NPM Security](https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities)
* [MacOS security and privacy guide](https://github.com/drduh/macOS-Security-and-Privacy-Guide)
* [Docker for Mac](https://github.com/docker/for-mac)
* [Using Node in Docker](https://www.docker.com/blog/keep-nodejs-rockin-in-docker/)
* [Bundler Audit](https://github.com/rubysec/bundler-audit)
* [OWASP Cheat Sheets](https://cheatsheetseries.owasp.org/)

### Malicious NPM packages

* <https://blog.bitsrc.io/malicious-npm-development-kit-a02401e6537e>
* <https://www.twilio.com/blog/2017/08/find-projects-infected-by-malicious-npm-packages.html>
* <https://news.ycombinator.com/item?id=17283394>
* [https://www.google.com/amp/s/www.zdnet.com/google-amp/article/malicious-npm-packages-caught-installing-remote-access-trojans/](https://www.google.com/amp/s/www.zdnet.com/google-amp/article/malicious-npm-packages-caught-installing-remote-access-trojans/?authuser=0)<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kb.chrisltd.com/cheat-sheets/security-tools.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.