Skip to content

docs(connectors): document the YesWeHack severity fallback and status mapping - #15930

Open
paulOsinski wants to merge 1 commit into
bugfixfrom
docs/yeswehack-connector-mappings
Open

docs(connectors): document the YesWeHack severity fallback and status mapping#15930
paulOsinski wants to merge 1 commit into
bugfixfrom
docs/yeswehack-connector-mappings

Conversation

@paulOsinski

Copy link
Copy Markdown
Contributor

Description

Documentation for two YesWeHack connector fixes shipping on this release line (paired Pro/connectors change):

  • The finding severity now resolves from the report's CVSS band, falling back to the triage priority, and then to the numeric CVSS score. Previously reports whose payload carried no recognizable band imported as Info.
  • Every YesWeHack workflow state now maps to an explicit finding status, so the tool page gains a mapping table: RTFS and Out Of Scope land as inactive/out of scope, Duplicate as an inactive duplicate, Invalid/Not Applicable/Spam as false positives, Won't Fix as risk accepted, Resolved/Auto Close as mitigated, and the open conversation states stay active.

English page only; translated pages are regenerated separately.

🤖 Generated with Claude Code

… mapping

The finding severity now falls back from the CVSS band to the triage
priority and then to the numeric CVSS score, and every YesWeHack workflow
state maps to an explicit finding status (RTFS lands as Out of Scope,
duplicates as inactive duplicates). Spell both out on the tool page.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@paulOsinski paulOsinski added this to the 3.3.100 milestone Sep 11, 2026
@github-actions github-actions Bot added the docs label Sep 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants