> 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/administration/repositories/upload-a-dependency-file-manually.md).

# Manually upload a dependency file

Learn how to upload a dependency file manually.

{% hint style="info" %}
*Keep in mind that this feature is accessible only to account admins.*
{% endhint %}

If you want to get the most out of the Fortify SCA tool, setting up an integration is the preferred way of working with your repositories.

However, if you want to test a specific dependency file for vulnerabilities, you can do so by manually uploading the file(s):

1. Go to [Repository Settings](https://debricked.com/app/en/repository-settings) on the left side menu.
2. Click **Manual scan** on the top right area of the table.
3. Upload the file(s) you want to scan.
4. Click **Start scan**.
5. Once the scan is completed, click **View results** to see all discovered vulnerabilities.

This action will create a repository named "<firstname.lastname@domain.com> - \<date>" and will add this scan as a commit within a repository.


---

# 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/administration/repositories/upload-a-dependency-file-manually.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.