Support for respecting Analysis state
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- html
- Domain
- frontend
Research direction
Start by tracing the rendering entry points for the summary, components table, and vulnerabilities table, then compare their handling with the CycloneDX 1.6 vulnerability analysis state specification. Done means states such as not_affected, false_positive, and resolved are consistently excluded or made controllable in all three views.
Written by the indexing model from the issue text.
Description
Feature request: When the VEX or VDR contains an analysis state it would be great to respect that in the visualization.
The spec: https://cyclonedx.org/docs/1.6/json/#vulnerabilities_items_analysis contains the state property to declare the occurrence of a vulnerability.
Thus in the summary, components and vulnerabilities table this should be respected maybe toggled to include them based on their state. Don't show "not_affected", "false_positive", "resolved".
- Dominant language
- HTML
- Stars
- 125
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CycloneDX/Sunshine
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in CycloneDX/Sunshine
Similar issues
-
Design only Leadership Survey SLFS
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
bcgov/digital-journeys#2293 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mermaid-js/mermaid-live-editor#2053 ·
Maintainers usually reply within 1 day
-
Toolkit
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
factory
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jessepollak/home#1455 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 94/100
lingdojo/kana-dojo#31226 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day