> For the complete documentation index, see [llms.txt](https://docs.debricked.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.debricked.com/product/open-source-select/compare-projects.md).

# Compare projects

Learn how to compare open source projects using OpenText Fortify Software Composition Analysis Open Source Select.

[Open Source Select](https://debricked.com/select/) enables you to compare projects side by side and gain insight into their individual strengths and weaknesses. You can compare aspects such as security, contributor commitment, and popularity.

To compare (up to three) projects:

1. Select the projects that you want to compare by clicking the **Add to comparison** (the scale icon) button on each project's card.
2. Click **Compare selected dependencies** below the search bar.

You can also:

* Click **Quick Compare** to see a comparison between the top three search results in the search page.
* Click **Compare** next to Similar dependencies in the project page to compare those projects.

### Choose open-source components with Fortify SCA's Open Source Select and Start Left - video guide

{% embed url="<https://www.youtube.com/watch?v=JCgA1DjAq8A>" %}


---

# 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.debricked.com/product/open-source-select/compare-projects.md?ask=<question>&goal=<user_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.