> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/technologies-as-assets/troubleshoot-repository-technology-detection.md).

# Troubleshoot repository technology detection

Resolve common technology detection issues. Review how composition percentages and technology metadata work.

## Frequently asked questions

### Can users manually tag a repository with a custom technology?

No. Technology detection is automated and cannot be manually overridden or supplemented.

The detection engine analyzes files during repository scans. Undetected custom frameworks do not appear in **Technologies**.

Use repository **Tags** for custom metadata. Tags appear in the repository side card.

### What happens when a new language is added?

The technology appears after the next repository scan. Select **Rescan** in the repository side card to update it immediately.

### Are technology percentages based on lines of code or file count?

Percentages represent each technology's proportional share of the repository codebase. File-level analysis calculates the proportions, which total 100%.

### Do technologies affect security scanning or policy evaluation?

Technologies are informational Asset Inventory metadata. They can inform scanner configuration and policy scoping.

## Troubleshoot technology detection

If a known technology is missing, review these causes and resolutions:

| Cause                                            | Resolution                                                                                |
| ------------------------------------------------ | ----------------------------------------------------------------------------------------- |
| **The repository has not been scanned recently** | Select the repository row, then select **Rescan** in the side-card actions.               |
| **All scanners are disabled for the repository** | Enable at least one scanner. The **Rescan** action is unavailable otherwise.              |
| **Technology files are on an unscanned branch**  | Confirm that the branch is included in the scanning scope.                                |
| **The technology is unsupported**                | Standard technologies are detected broadly. Proprietary frameworks might not be detected. |


---

# 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://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/technologies-as-assets/troubleshoot-repository-technology-detection.md?ask=<question>&goal=<endgoal>
```

`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.