Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 78 · Caution

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 6 caught lines

Download .patch

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -25,1 +25,0 @@
-<summary>Security best practices</summary> > 🔒 **Important**: Your SonarQube token is a sensitive credential. Follow these security practices: **When using CLI
@@ -104,1 +103,0 @@
-<summary>Claude Code</summary> * To connect with SonarQube Cloud: ```bash claude mcp add sonarqube \ --env SONARQUBE_TOKEN=$SONAR_TOKEN \ --env SONARQUBE_ORG=$S
@@ -129,1 +127,0 @@
-<summary>Codex CLI</summary> Manually edit the configuration file at `~/.codex/config.toml` and add the following configuration: * To connect with SonarQube Clo
@@ -171,1 +168,0 @@
-<summary>Gemini CLI</summary> > **Note:** The Gemini CLI extension has moved to the [sonarqube-agent-plugins](https://github.com/SonarSource/sonarqube-agent-plu
@@ -199,1 +195,0 @@
-<summary>GitHub Copilot CLI</summary> After starting Copilot CLI, run the following command to add the SonarQube MCP server: ```bash /mcp add ``` You will have 
@@ -392,1 +387,0 @@
-<summary>Windsurf</summary> SonarQube MCP Server is available as a Windsurf plugin. Follow these instructions: 1. Open Windsurf **Settings** > **Cascade** > **M

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of r10. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: sonarqube: Collapsed <details> block carrying instructions (KillerSkills verdict caution 78)

## What the honeypot observed
KillerSkills ran **sonarqube@r10** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 78/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/docker/sonarqube/r10

## Findings with a location
- `README.md:392` · Collapsed <details> block carrying instructions — README.md:392 · Collapsed <details> block carrying instructions
- `README.md:104` · Collapsed <details> block carrying instructions — README.md:104 · Collapsed <details> block carrying instructions
- `README.md:199` · Collapsed <details> block carrying instructions — README.md:199 · Collapsed <details> block carrying instructions
- `README.md:25` · Collapsed <details> block carrying instructions — README.md:25 · Collapsed <details> block carrying instructions
- `README.md:171` · Collapsed <details> block carrying instructions — README.md:171 · Collapsed <details> block carrying instructions
- `README.md:129` · Collapsed <details> block carrying instructions — README.md:129 · Collapsed <details> block carrying instructions

## Proposed change
The attached patch removes the 6 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._

Open the issue on GitHub (SonarSource/sonarqube-mcp-server)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork SonarSource/sonarqube-mcp-server --clone && cd sonarqube-mcp-server
curl -s https://killerskills.ai/skills/docker/sonarqube/r10/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/r10 && git commit -am "sonarqube: Collapsed <details> block carrying instructions"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/docker/sonarqube/r10/patch.md)

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.