> 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.md).

# Technologies as assets

Use the Asset inventory to identify, filter, and analyze the technical makeup of repositories. Access technology tags in the **Repositories** table and view detailed percentage breakdowns within repository side cards.

## Prerequisites

Before viewing repository technologies, verify the following:

| Prerequisite              | Description                                                                                         |
| ------------------------- | --------------------------------------------------------------------------------------------------- |
| **License**               | An active Cortex Cloud license with Application Security entitlements                               |
| **RBAC role**             | A role with permissions to view the Asset Inventory and repository assets                           |
| **VCS Integration**       | At least one Version Control System (GitHub, GitLab, Bitbucket, Azure DevOps) integrated and active |
| **Repository onboarding** | Target repositories onboarded and scanned by Application Security                                   |

## Navigate to repository technologies

1. In your tenant, navigate to Posture Management → **Asset Inventory**.
2. Select **Repositories** (under **Code**).

   The Repositories table displays all onboarded repositories with associated metadata, including detected technologies.

## View technologies in the Repositories table

The Repositories table includes a **Technologies** column that displays the technologies detected in each repository. If it is not displayed automatically, you can add it through the table Menu Settings.

#### Technologies column behavior

* Each technology appears as a **tag** containing the technology icon and name (for example, a JavaScript icon followed by **javascript**)
* If a repository contains multiple technologies, the column displays a truncated list showing the first three. Hover over the indicator to view the full list
* The technology data is derived from the repository file composition and is updated with each repository scan

### Filter repositories by technology

Use the **Technologies** filter to locate repositories that contain a specific technology.

1. In the Repositories table, select the filter controls.
2. Select **Technologies** from the available filter fields.
3. Enter or select the technology name (for example, **Python**).

   The table updates to display only matching repositories. You can combine multiple filters to narrow the scope.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>The filter supports wildcard filtering and is case-insensitive.</p></div>

### View technologies in the repository side card

Select any repository row in the table to open the repository side card, which displays detailed properties.

**Technologies property**: The Technologies property in the side card displays each detected technology with the following details:

* **Icon**: A technology-specific icon for visual identification
* **Name**: The technology name (for example, python)
* **Percentage (tooltip)**: Hover over a tag to view a tooltip showing the percentage of the codebase attributed to that technology. Percentages sum to 100%

## Next steps

[Troubleshoot repository technology detection](/application-security/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/technologies-as-assets/troubleshoot-repository-technology-detection.md)


---

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