> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/snyk-cli/snyk-cli/scan-and-maintain-projects-using-the-cli/snyk-cli-for-open-source/review-the-snyk-open-source-cli-results.md).
# Review the Snyk Open Source CLI results
After you run the `snyk test` command in the CLI, the Snyk Open Source test results are displayed. The report of results includes a summary of the test findings, a list of vulnerability issues detected, and descriptive information about the Snyk Project tested.
Snyk Open Source CLI test results
## Summary of test findings
The summary of the test findings at the beginning of the report of results shows the following:
Snyk Open Source CLI dependencies tested, issues and vulnerabilities found
* The number of direct and transitive dependencies scanned
* Total number of issues found across one or more paths
* The number of paths through which vulnerable dependencies are introduced
## List of vulnerability issues detected by Snyk Open Source
The list of issues discovered in the Snyk Open Source test includes the following sections.
### Issues to fix by upgrading
These are issues that can be fixed by upgrading a direct dependencies version. They contain the following information:
* Which dependency to upgrade to resolve the issue
* The issue type
* The [severity rating](/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/severity-levels.md) for the issue
* A link to the related issue in the [Snyk Vulnerability Database](https://security.snyk.io/)
* The dependency through which this vulnerability is introduced and its path
### Issues with no direct upgrade or patch
These are issues that cannot be resolved by upgrading a direct dependency. They contain the same information as the issues to fix by upgrading, with versions in which the vulnerability could be fixed if the dependency were upgradeable.
### License Issues
License issues are determined by the [license policy](/scan-fix-and-prevent/prevent/policies/license-policies.md) of your Snyk Organization. License issues contain the following information:
* Type of license
* License severity as determined by the license policy of your Snyk Organization
* Link to the [Snyk Vulnerability Database](https://security.snyk.io/), which provides more information about the license
* Dependency path through which this license is introduced
## Descriptive information about the Snyk Project scanned
The descriptive information about the test results includes the following details:
* **Organization**: The Snyk ID or internal name of the Organization under which the test ran. For more information, see [`--org=ORG_ID>` option](/developer-tools/snyk-cli/snyk-cli/commands/test.md#org-less-than-org_id-greater-than) in the `snyk test` help.
* **Package manager**: The package manager associated with this Open Source scan
* **Target File**: The target file which was scanned for Open Source vulnerabilities
* **Project Name**: The name of the directory in which this Project is located
* **Open Source**: Information about whether or not this scan was performed on an Open Source Project.
* **Project Path**: The path through which the target file is introduced
* **Local Snyk Policy**: Information about whether this scan was performed on an Open Source Project. For more information, see [The .snyk file](/scan-fix-and-prevent/prevent/policies/the-.snyk-file.md).
* **Licenses**: Information about whether this Project was scanned for license issues
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.snyk.io/developer-tools/snyk-cli/snyk-cli/scan-and-maintain-projects-using-the-cli/snyk-cli-for-open-source/review-the-snyk-open-source-cli-results.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.