Skip to content

Docs: Clarify SCA criticality filter and legacy urgency compatibility #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Ibrahimrahhal wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Docs: Clarify SCA criticality filter and legacy urgency compatibility #91

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion sca.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,12 +133,14 @@ description: "Dependency Scanning, also known as Software Composition Analysis (

Use filters on the Dependencies view to narrow SCA results:
- **Search**: Find issues by CVE, package name, or summary
- **Severity**: Focus on Critical, High, Medium, or Low findings
- **Criticality**: Focus on Critical, High, Medium, or Low findings
- **Ecosystem**: Limit results to a specific package ecosystem
- **Project**: Filter to a specific project by name (shows only projects you can access)
- **License**: Filter by dependency license
- **Fix Available**: Show only issues with a known fix

When sharing filtered Dependencies views or exporting filtered SCA CSV results, Corgea uses the `criticality` query parameter. Legacy links that use `urgency` are still supported.

### Supported Ecosystems

<Accordion title="View All 25+ Supported Ecosystems">
Expand Down