# Scan and maintain projects using the CLI

This group of pages provides detailed "how-to" information for the Snyk CLI. The navigation is alphabetical by keyword. The same list of pages follows in the categories Scanning projects, Monitoring projects, and Maintaining projects.

## Scanning projects

* [The **.snyk** file](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/the-.snyk-file)
* [A **.snyk** policy file in a different directory from the manifest file](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/using-a-.snyk-file-in-a-separate-directory-than-the-manifest-file)
* [Failing **builds** in Snyk CLI](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/advanced-failing-of-builds-in-snyk-cli)
* [**Ignore** vulnerabilties using Snyk CLI](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/ignore-vulnerabilities-using-snyk-cli)
* [**Invalid string length** error when scanning projects](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/invalid-string-length-error-when-scanning-projects)
* [Scan all unmanaged **JAR files**](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/scan-all-unmanaged-jar-files)
* [How to select the **organization** to use in the CLI](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/how-to-select-the-organization-to-use-in-the-cli)
* [**Setup.py file** failing to scan or finding zero dependencies](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/why-is-my-setup.py-file-failing-to-scan-or-finding-0-dependencies)
* [**Severity thresholds** for CLI tests](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/set-severity-thresholds-for-cli-tests)
* [**Test public npm packages** before use](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/test-public-npm-packages-before-use)
* [**Test public repositories** before use](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/test-public-repositories-before-use)
* [CLI **test results**](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/view-cli-test-results)
* [Differences in **vulnerability counts** across environments](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/differences-in-vulnerability-counts-across-environments)

## Monitoring projects

* [**Monitor** your projects at regular intervals](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/monitor-your-projects-at-regular-intervals)
* [Group **projects** for monitoring](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/grouping-projects-by-branch-or-version)

## Maintaining projects

* [Automatic **fixing** with Snyk Fix](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/automatic-remediation-with-snyk-fix)
* [**Log4shell** command use](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/how-to-use-the-log4shell-command)
* [@**snyk/protect** package](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/protect-your-code-with-patches)
* [Fix **vulnerabilities** using the Snyk CLI](https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities/fix-vulnerabilities-using-the-snyk-cli)


---

# Agent Instructions: 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://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/snyk-cli/test-for-vulnerabilities.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.