> ## Documentation Index
> Fetch the complete documentation index at: https://docs.endorlabs.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Search for Open Source Packages
> Search open source packages and review the security, dependency, and license details of a specific package version.
Open source packages provide flexible, customizable software solutions that can reduce development costs and time, while also fostering innovation through community collaboration.
To search for open source packages:
1. Select **Discovery** > **Open Source Packages** from the left sidebar.
2. Type in the search bar to look for open source packages and click **Search Open Source Packages**.
3. Choose the **Ecosystem** and click **Search Open Source Packages** to look for packages by their ecosystem.
4. Select a search result to review the list of package versions, their dependencies, and Endor security scores.
5. Select a package version to open its details page.
## Review package version details
The package version details page shows the package name and version, Endor security score, and a link to the source repository when available. Use the version selector next to the package name to switch to another version of the same package. See [Endor scores](/scan/sca/scores) to learn how Endor Labs calculates these scores.
The package version details page organizes information into the following tabs:
1. Select **Overview** to review the following information:
* **Package Version Scores**: The **Security**, **Activity**, **Popularity**, and **Quality** Endor Scores for the version.
* **Score Factors**: The factors that contribute to each score. Click **All Score Factors** to see the complete list.
* **Finding Risk Matrix**: The package version's findings mapped by severity and finding category. Use the category selector to filter the matrix.
* **Top Metadata**: Dependency counts, dependency pinning, dependency scopes, and declared and discovered licenses.
2. Select **Findings** to review the security findings for the package version. You can filter findings by severity, finding category, or other criteria, and save frequently used filters for later.
3. Select **Dependencies** to review the packages this version depends on. Choose **Packages** or **AI Models** to switch between dependency types.
4. Select **Dependency Graph** to see a visual graph of how the package version's dependencies connect.
## Export an SBOM or VEX for a package version
You can generate a software bill of materials (SBOM) or a Vulnerability Exploitability eXchange (VEX) document for a single package version directly from its details page.
1. Click **Export** in the top right corner.
2. Select **SBOM**.
3. Optionally, click **All packages included** to select specific packages instead. If you leave it as is, Endor Labs includes every package in the export.
4. Choose a **Format** from **CycloneDX** or **SPDX**.
* Choose whether to export as an **Application** or a **Library**. If you choose **Application**, enter an **Application Name**.
* Choose a **File Format** from **JSON** or **XML**.
* Enter an **Application Name**.
* Choose a **File Format** from **JSON** or **Tag-Value**.
5. Optionally, select **Include test dependencies**.
6. Click **Export** to download the SBOM.
1. Click **Export** in the top right corner.
2. Select **VEX**.
3. Optionally, click **All packages included** to select specific packages instead. If you leave it as is, Endor Labs includes every package in the export.
4. Choose whether to export as an **Application** or a **Library**.
If you choose **Application**, enter an **Application Name**.
5. Choose a **File Format** from **JSON** or **XML**.
6. Optionally, select **Include test dependencies**.
7. Click **Export** to download the VEX document.
See [Export SBOMs and VEX](/inventory-insights/sbom/exporting-sboms) to learn about each export field and format in detail.