Skip to content

Commit 177d13b

Browse files
Add 'Dependency chain' heading to security findings page (#2686)
* Add 'Dependency chain' heading to security findings page * Update docs/organizations/managing-security-and-risk.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --------- Co-authored-by: mark-rln <mark-rln@users.noreply.github.com> Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
1 parent 34495c7 commit 177d13b

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

docs/organizations/managing-security-and-risk.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,8 @@ On the right section, you can view the filtered list of findings. Each finding c
9999

100100
![Security and risk management finding page](images/security-risk-management-finding-details.png)
101101

102+
### Dependency chain {: id="dependency-chain"}
103+
102104
For findings on transitive dependencies, the finding also displays the **dependency chain**: the ordered path from a direct (top-level) dependency in your manifest down to the vulnerable package (for example, `direct-package → intermediate-package → vulnerable-package`). This helps you identify which of your direct dependencies you need to update to resolve the finding.
103105

104106
![Security and risk management finding dependency chain](images/security-risk-management-finding-dependency-chain.png)

0 commit comments

Comments
 (0)