> For the complete documentation index, see [llms.txt](https://docs.safetycli.com/safety-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.safetycli.com/safety-docs/safety-cli/system-wide-developer-machine-scanning.md).
# System-Wide Developer Machine Scanning
## Shift Left: Protection at Every Stage of Development
Performing scans in single project repositories or in CI/CD and Production is insufficient to provide true end-to-end security. Safety CLI 3 allows developers to detect *all* Python installations and vulnerabilities in their environment by performing system-wide scans of development machines.
Once Safety CLI is installed and you have authenticated, we follow a similar process to the normal directory-specific **`safety scan`**.
In your terminal, run the following command:
```
safety system-scan
```
Running **`safety system-scan`** will:
* Scan your entire development machine for Python package files, requirements files and Python virtual environments, indexing all the packages found.
* Conduct a security analysis of these packages against known security vulnerabilities and malicious package lists.
* Identify known vulnerabilities in these packages, including their location and version.
* Provide fix recommendations.
Once complete, your terminal will show a summary of the vulnerable packages that were found and recommended actions.
{% hint style="info" %}
If the safety `system-scan` command is not found, **or your safety version is less than 3.0,** you need to [install Safety version 3](/safety-docs/safety-cli/installation-and-authentication.md) before continuing below.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.safetycli.com/safety-docs/safety-cli/system-wide-developer-machine-scanning.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
