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

# Working with project filters

> Learn how to implement and use project filters to search, prioritize, and manage projects across your organization. Includes an interactive filter builder.

Filters enable targeted queries based on attributes such as severity, package ecosystems, dependency resolution, and platform source.

This guide explains how filters work, how to apply and combine them effectively, and provides practical examples to support triage, audit, and reporting workflows across large codebases.

## Access project filters

Perform the following steps to apply filters to the project list.

1. Select **Projects** from the left sidebar.
2. Filter your projects using the list of available filters in the filter bar.
3. Toggle the **Advanced** option in the filter bar to apply API-style filters.

You can combine multiple filters to create more specific searches and narrow down the project list based on multiple criteria.

## How filters work

Each filter consists of three parts.

* **Field**: The attribute you want to filter (for example, `Package Count` and `Platform Source`).
* **Operator**: The comparison logic (for example, `equals`, `greater than`, and `in`).
* **Value**: The target value to evaluate (for example, `npm` and `100`).

Project filters use standard comparison operators to evaluate criteria. See [Filter operators](https://docs.endorlabs.com/developers-api/rest-api/using-the-rest-api/filters.md#operators) for detailed information about available operators and their usage.

When you apply multiple filters, the system combines them using logical AND operations across filters for different fields and logical OR operations across filters for the same field.

For example:

* **Filter 1**: `Package Ecosystems contains: npm`
* **Filter 2**: `Platform Source in: GitHub`
* **Filter 3**: `Package Count: greater than 1`
* **Filter 4**: `Reachability Analysis Status greater than or equal to: 90%`

![Multiple filters](https://mintcdn.com/endorlabs-b4795f4f/deISr2DfATZg293W/images/best-practices/project-filters/project-filters/multiple-filters.webp?fit=max\&auto=format\&n=deISr2DfATZg293W\&q=85\&s=4d9ea0df181c8c32c34e3523d29057be)

This combination returns only projects that use npm packages, are from GitHub, have more than one package, and have a reachability analysis status of at least 90%.

## Filter implementation techniques

You can use the following filter types to manage your projects effectively.

* [Preset filters](#preset-filters): Use predefined UI-based filters to quickly segment projects by common attributes.
* [Filter projects using API](#filter-projects-using-api): Use advanced syntax for complex queries and logical combinations.
* [Saved filters](#saved-filters): Save a filter query and reapply it to the Projects table without building it again.

### Preset filters

The following examples demonstrate how to apply preset filters for common project scenarios.

#### Filter projects by custom tags

Use custom tags to filter projects based on environment or predefined labels assigned during project initialization or scan configuration.

For example, to view only projects related to SAST, use the `Custom Tags contains: sast` filter.

![filter by custom tags](https://mintcdn.com/endorlabs-b4795f4f/deISr2DfATZg293W/images/best-practices/project-filters/project-filters/filter-custom-tags.webp?fit=max\&auto=format\&n=deISr2DfATZg293W\&q=85\&s=1580b27a6908b34830c83b56fc1d9f9e)

#### Filter projects by findings severity

Prioritize remediation efforts by filtering projects based on the severity of security findings. You can select from **Critical (C)**, **High (H)**, **Medium (M)**, or **Low (L)** severity filters to target different priority levels.

For example, to identify projects with critical findings, select the **C** filter.

![filter by severity](https://mintcdn.com/endorlabs-b4795f4f/deISr2DfATZg293W/images/best-practices/project-filters/project-filters/filter-finding-severity.webp?fit=max\&auto=format\&n=deISr2DfATZg293W\&q=85\&s=e6b5624341c4b592ae59dbafd0687811)

#### Filter projects by package ecosystem

Use package ecosystem filters to segment projects by language or package manager. Apply targeted policies, such as stricter vulnerability thresholds for JavaScript or license compliance checks for Java.

For example, to focus on PHP projects for a security assessment, use the `Package Ecosystems contains: Packagist` filter.

![filter by package ecosystem](https://mintcdn.com/endorlabs-b4795f4f/deISr2DfATZg293W/images/best-practices/project-filters/project-filters/filter-package-ecosystem.webp?fit=max\&auto=format\&n=deISr2DfATZg293W\&q=85\&s=eb98e9241ff0b1add02dfff7692d0dd2)

#### Filter projects by source platform

Use platform source filters to segment projects by their source platform and correlate findings with platform-native security tools like GitHub's Dependabot alerts or GitLab's vulnerability scanning.

For example, to identify projects analyzed from GitLab, use the `Platform Source in: GitLab` filter.

![filter by source platform](https://mintcdn.com/endorlabs-b4795f4f/deISr2DfATZg293W/images/best-practices/project-filters/project-filters/filter-source-platform.webp?fit=max\&auto=format\&n=deISr2DfATZg293W\&q=85\&s=adf9b6840ca10c6238a722258b21fa70)

#### Filter projects by dependency resolution quality

Use dependency resolution status to identify projects with resolution issues that impact security analysis accuracy. You can filter by a single value or a range of percentages.

For example, to identify projects with poor dependency resolution, use the **Range** filter to find projects with `Dependency Resolution Status greater than 0% and less than 50%`.

![filter by resolution](https://mintcdn.com/endorlabs-b4795f4f/deISr2DfATZg293W/images/best-practices/project-filters/project-filters/filter-dependency-resolution-status.webp?fit=max\&auto=format\&n=deISr2DfATZg293W\&q=85\&s=babbe9f8df560e521d3d4c0eedd4c55f)

#### Filter projects by scan timestamp

Use last scanned filters to identify projects with stale security data that require fresh scans for current security posture. You can select from predefined time ranges or use the calendar to select a specific date.

For example, to identify projects scanned within the last 24 hours, use the `Last Scanned: Last Day` filter.

![filter by last scanned](https://mintcdn.com/endorlabs-b4795f4f/deISr2DfATZg293W/images/best-practices/project-filters/project-filters/filter-last-scanned.webp?fit=max\&auto=format\&n=deISr2DfATZg293W\&q=85\&s=2183af616f23f032e7f76fbd7dd33ec7)

#### Filter projects by complexity

Identify projects based on their size and complexity, which may require different levels of security attention and resources.

For example, to focus on large projects with extensive dependency trees, use the `Package Count: greater than 100` filter.

![filter by complexity](https://mintcdn.com/endorlabs-b4795f4f/deISr2DfATZg293W/images/best-practices/project-filters/project-filters/filter-complexity.webp?fit=max\&auto=format\&n=deISr2DfATZg293W\&q=85\&s=e6bb01e84ebd182478ae2061d93045ff)

#### Filter projects by reachability analysis status

Use reachability analysis status to identify projects based on the success rate of call graph generation and reachability analysis. You can filter by a single value or a range of percentages.

For example, to identify projects with successful reachability analysis, use the `Reachability Analysis Status greater than or equal to: 90%` filter.

![filter by reachability status](https://mintcdn.com/endorlabs-b4795f4f/deISr2DfATZg293W/images/best-practices/project-filters/project-filters/filter-reachability-analysis-status.webp?fit=max\&auto=format\&n=deISr2DfATZg293W\&q=85\&s=8d917849c9b83aaa78e44e9b48938a7f)

### Filter projects using API

For complex queries, use the advanced filter syntax to combine multiple attributes and apply logical operators. Use the [Project filter builder](#interactive-filter-builder) to assemble conditions interactively.

The following table lists the available attributes for project filters.




&#x20; \- Attribute: Project UUID
&#x20; Description: Filters projects by their unique identifier.

&#x20; \- Attribute: Name
&#x20; Description: Filters projects by the display name of the project.

&#x20; \- Attribute: Custom Tags
&#x20; Description: Filters projects by custom tags set during project setup or scan configuration.

&#x20; \- Attribute: Last Scanned
&#x20; Description: Filters projects based on the timestamp of the last successful scan.

&#x20; \- Attribute: Package Count
&#x20; Description: Filters projects by the total number of packages resolved in the project.

&#x20; \- Attribute: Package Ecosystems
&#x20; Description: Filters projects based on the language-specific package ecosystems they use.

&#x20; \- Attribute: Dependency Resolution Status
&#x20; Description: Filters projects by the percentage of resolved dependencies in the project.

&#x20; \- Attribute: Reachability Analysis Status
&#x20; Description: Filters projects based on the success rate of reachability analysis through call graph generation.

&#x20; \- Attribute: Critical Findings Count
&#x20; Description: Filters projects based on the number of critical-severity findings in the project.

&#x20; \- Attribute: High Findings Count
&#x20; Description: Filters projects based on the number of high-severity findings in the project.

&#x20; \- Attribute: Medium Findings Count
&#x20; Description: Filters based on the number of medium-severity findings in the project.

&#x20; \- Attribute: Low Findings Count
&#x20; Description: Filters projects based on the number of low-severity findings in the project.

&#x20; \- Attribute: Dismissed Findings Count
&#x20; Description: Filters projects by the number of findings that users dismissed. Useful for reviewing triage quality.

&#x20; \- Attribute: Total Findings Count
&#x20; Description: Filters projects based on the total number of findings detected in a project.

&#x20; \- Attribute: Platform Source
&#x20; Description: Filters projects based on source platform and helps narrow results by version control origin such as GitHub, GitLab, or Bitbucket.

&#x20; \- Attribute: Automated Scan Enabled
&#x20; Description: Filters projects by whether automated scanning is enabled.

&#x20; \- Attribute: Total Vulnerabilities
&#x20; Description: Filters projects by the total number of vulnerabilities detected across all severity levels.

&#x20; \- Attribute: Critical Vulnerabilities
&#x20; Description: Filters projects by the number of critical-severity vulnerabilities detected.

&#x20; \- Attribute: High Vulnerabilities
&#x20; Description: Filters projects by the number of high-severity vulnerabilities detected.

&#x20; \- Attribute: Medium Vulnerabilities
&#x20; Description: Filters projects by the number of medium-severity vulnerabilities detected.

&#x20; \- Attribute: Low Vulnerabilities
&#x20; Description: Filters projects by the number of low-severity vulnerabilities detected.

&#x20; \- Attribute: Direct Dependencies
&#x20; Description: Filters projects by the count of dependencies declared directly in project manifests.

&#x20; \- Attribute: Transitive Dependencies
&#x20; Description: Filters projects by the count of transitive (indirect) dependencies pulled in through direct dependencies.

&#x20; \- Attribute: Outdated Dependencies
&#x20; Description: Filters projects by the number of dependencies with newer versions available.

&#x20; \- Attribute: Unmaintained Dependencies
&#x20; Description: Filters projects by the number of dependencies that are no longer actively maintained.


&#x20;&#x20;

### Interactive filter builder

### Project Filter Builder

Construct advanced project filters using the API-style syntax.

Build your filter

* Add condition

Generated filter expression

<pre />

Copy to clipboard

Copy this expression and paste it into the **Advanced Filter** box in
the Projects UI.

### API filter use cases

The following examples demonstrate how to combine these attributes for common security and compliance workflows.

> [accordion] Identify high-risk GitHub projects
>
> Find GitHub projects with more than 5 critical findings and a reachability analysis status below 80%.
>
> ```bash theme={null}
> spec.platform_source == PLATFORM_SOURCE_GITHUB and spec.finding_counts.critical > 5 and spec.package_coverage.call_graph_success_rate < 0.8
> ```

> [accordion] Audit stale projects with risks
>
> Identify projects not scanned in the last 7 days that still have outdated dependencies.
>
> ```bash theme={null}
> spec.last_scanned < now(-168h) and spec.dependency_counts.outdated > 0
> ```

> [accordion] Identify projects with low dependency resolution quality
>
> Find projects where dependency resolution is below 90%, which may indicate incomplete security analysis.
>
> ```bash theme={null}
> spec.package_coverage.success_rate < 0.9
> ```

> [accordion] Find large projects with high vulnerability density
>
> Identify projects with more than 100 total packages that also have a high number of critical vulnerabilities.
>
> ```bash theme={null}
> spec.package_coverage.total > 100 and spec.vulnerability_counts.total.critical > 20
> ```

> [accordion] Audit projects with high triaged findings
>
> Find projects where more than 50 findings have been dismissed, useful for auditing triage quality.
>
> ```bash theme={null}
> spec.finding_counts.dismissed > 50
> ```

> [accordion] Triage critical vulnerabilities by ecosystem
>
> Focus on npm projects with a high number of critical vulnerabilities.
>
> ```bash theme={null}
> spec.package_coverage.ecosystems contains ECOSYSTEM_NPM and spec.vulnerability_counts.total.critical > 10
> ```

## Saved filters

Saved filters store a filter query on the Projects table so you can reapply it without building it again. Each saved filter appears in the **Saved Filters** list in the filter bar.

To create a saved filter:

1. Select **Projects** from the left sidebar.
2. Apply the filters you want to save in the filter bar. To enter a query instead, select **Toggle Advanced Filter Mode** and type or build your query.
3. Click **Saved Filters**.
4. Click **Save Current**.
5. Enter a name in the **Choose filter name** field.
6. Click **Save**.

To apply a saved filter, click **Saved Filters** in the filter bar and select the filter.

### Manage saved filters

To edit a saved filter:

1. Select **User menu** > **Settings** from the left sidebar.
2. Select **Saved Filters**.
3. Click **Edit** next to the filter you want to edit.
4. Update the name, query, or tags.
5. Click **Update**.

To delete a saved filter:

1. Select **User menu** > **Settings** from the left sidebar.
2. Select **Saved Filters**.
3. Click the vertical three dots next to the filter you want to delete, and select **Delete**.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.