> 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/overview/getting-started/running-debricked.md).

# Running Fortify SCA

Learn about all the different ways of using OpenText Fortify Software Composition Analysis.

You can run Fortify SCA in any of the following ways:

* **Web**: [The Fortify SCA web app](https://debricked.com/app/en/login) enables a browser-based experience, providing all functions, including security and license scanning, automation, reporting, and more.
* **CLI**: [The Fortify SCA Command Line Interface](/tools-and-integrations/cli/debricked-cli.md) enhances open-source security and license compliance for your project through the command prompt. It allows you to conduct vulnerability scans on your local machine and seamlessly integrate Fortify SCA into your pipeline.
* **API**: [The Fortify SCA APIs](/tools-and-integrations/debricked-apis.md) allow you to integrate our service into your code, CI pipelines, and more.
* **Browser**: [The Fortify SCA Select Browser Extension](/product/open-source-select/debricked-select-browser-extension.md) integrates the **Select** option directly into your browser, allowing you to examine an open-source project's health metrics and license information without leaving the page.


---

# 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/overview/getting-started/running-debricked.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.