Skip to content

fix(vscode): DQS tooltip shows 🚨 SECURITY BREACH on Z201 status (LSP-FIX-015) - #62

Merged
PythonWoods-Dev merged 13 commits into
mainfrom
fix/lsp-state-and-dqs
Jul 28, 2026
Merged

fix(vscode): DQS tooltip shows 🚨 SECURITY BREACH on Z201 status (LSP-FIX-015)#62
PythonWoods-Dev merged 13 commits into
mainfrom
fix/lsp-state-and-dqs

Conversation

@PythonWoods-Dev

Copy link
Copy Markdown
Collaborator

Objective

Corrects the DQS tooltip rendering when zenzic score returns status: 'security_breach' (Z201 — credential detected).

Root Cause

The tooltip showed category checkmarks (✓ links, ✓ credentials) even when Z201 forced the score to 0. This was misleading — a credential breach had been detected but the UI displayed green checkmarks.

Changes

src/extension.ts

When status === 'security_breach':

  • Status bar: Zenzic DQS: SECURITY BREACH
  • Tooltip: 🚨 ZENZIC — SECURITY BREACH DETECTED 🚨 with rotation instructions and Z201 reference.

Normal (non-breach) rendering is unchanged.

Acceptance Criteria

  • ✅ Z201 workspace shows clear Security Breach warning in DQS tooltip.
  • just verify passes 100% (ESLint, tsc, REUSE).

…on pattern

Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
…sion baseline

Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
…st formatting

Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
…FIX-015)

When zenzic score --json returns status='security_breach' (Z201 — credential
detected), the DQS status bar and tooltip now clearly communicate the breach:

- Status bar: ' Zenzic DQS: SECURITY BREACH' (was: ' Zenzic DQS: 0/100')
- Tooltip: 🚨 ZENZIC — SECURITY BREACH DETECTED 🚨 with remediation instructions
  instead of misleading green '✓' category checkmarks.

Normal (non-breach) status bar and tooltip rendering is unchanged.

Acceptance Criteria (LSP-FIX-015 Fix 3):
- A workspace with a Z201 error displays a clear Security Breach warning
  in the DQS tooltip.

Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
…(LSP-FEAT-003)

Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
@PythonWoods-Dev
PythonWoods-Dev force-pushed the fix/lsp-state-and-dqs branch from 362b5c5 to 08e618b Compare July 28, 2026 15:17
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

…release sequence

Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
Signed-off-by: PythonWoods <gianluca.catalano@gmail.com>
@PythonWoods-Dev
PythonWoods-Dev merged commit 664bf4f into main Jul 28, 2026
3 checks passed
@PythonWoods-Dev
PythonWoods-Dev deleted the fix/lsp-state-and-dqs branch July 28, 2026 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants