jramos/cve-dashboard
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update 'Reporting page' references to 'Vulnerability Triage'

Browse Source 
Updated all human-readable references in documentation to reflect the
page rename. File path citations in security-audit-2026-04-01.md
(ReportingPage.js:51) are left unchanged as the file itself was not
renamed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
jramos
2026-04-02 10:15:51 -06:00
parent a0a8979c63
commit 5102a2c5b4
2 changed files with 161 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/security-posture-workflow-diagrams.md
View File

@@ -9,7 +9,7 @@ Renders natively in GitHub, GitLab, and most modern documentation tools.
```mermaid
flowchart TD
START([Open Reporting Page]) --> SYNC
START([Open Vulnerability Triage Page]) --> SYNC
SYNC["① Sync & Sort<br/>Click Sync · Sort Due Date ascending"]
SYNC --> DUE{Overdue<br/>findings?}
@@ -94,11 +94,11 @@ flowchart TD
## Diagram 2 — FP Workflow Badge Status Decision Tree
What to do when a finding already has a workflow badge in the Reporting page.
What to do when a finding already has a workflow badge in the Vulnerability Triage page.
```mermaid
flowchart LR
A([Finding in<br/>Reporting Page]) --> B{"Check<br/>Workflow column"}
A([Finding in<br/>Vulnerability Triage]) --> B{"Check<br/>Workflow column"}
B -->|No badge| C["UNTRIAGED<br/>No action on record"]
C --> C1(["Follow the<br/>Step 1–5 triage workflow ↑"])