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. 55 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 8 caught lines
Download .patchdiff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -102,1 +102,0 @@
-<summary><b>Claude Desktop</b> · <code>claude_desktop_config.json</code></summary> ```json { "mcpServers": { "filesystem": { "command": "unwind", "a
@@ -117,1 +116,0 @@
-<summary><b>Claude Code</b> · <code>.mcp.json</code></summary> ```json { "mcpServers": { "filesystem": { "command": "unwind", "args": ["run", "--",
@@ -134,1 +132,0 @@
-<summary><b>Cursor</b> · <code>~/.cursor/mcp.json</code></summary> ```json { "mcpServers": { "filesystem": { "command": "unwind", "args": ["run", "-
@@ -149,1 +146,0 @@
-<summary><b>VS Code</b> (MCP) · <code>.vscode/mcp.json</code></summary> ```json { "servers": { "filesystem": { "command": "unwind", "args": ["run",
@@ -164,1 +160,0 @@
-<summary><b>Cline</b> · <code>cline_mcp_settings.json</code></summary> ```json { "mcpServers": { "filesystem": { "command": "unwind", "args": ["run"
@@ -179,1 +174,0 @@
-<summary><b>Windsurf</b> · <code>~/.codeium/windsurf/mcp_config.json</code></summary> ```json { "mcpServers": { "filesystem": { "command": "unwind",
@@ -194,1 +188,0 @@
-<summary><b>Goose</b> · <code>~/.config/goose/config.yaml</code></summary> ```yaml extensions: filesystem: type: stdio cmd: unwind args: ["run", "--
@@ -207,1 +200,0 @@
-<summary><b>Zed</b> · <code>settings.json</code></summary> ```json { "context_servers": { "filesystem": { "command": { "path": "unwind", "args": ["r
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.0. 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: rollback-mcp: Collapsed <details> block carrying instructions (KillerSkills verdict caution 55)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 55/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/pypi/rollback-mcp/0.2.0 ## Findings with a location - `README.md:164` · Collapsed <details> block carrying instructions — README.md:164 · Collapsed <details> block carrying instructions - `README.md:149` · Collapsed <details> block carrying instructions — README.md:149 · Collapsed <details> block carrying instructions - `README.md:194` · Collapsed <details> block carrying instructions — README.md:194 · Collapsed <details> block carrying instructions - `README.md:134` · Collapsed <details> block carrying instructions — README.md:134 · Collapsed <details> block carrying instructions - `README.md:179` · Collapsed <details> block carrying instructions — README.md:179 · Collapsed <details> block carrying instructions - `README.md:117` · Collapsed <details> block carrying instructions — README.md:117 · Collapsed <details> block carrying instructions - `README.md:207` · Collapsed <details> block carrying instructions — README.md:207 · Collapsed <details> block carrying instructions - `README.md:102` · Collapsed <details> block carrying instructions — README.md:102 · Collapsed <details> block carrying instructions ## Proposed change The attached patch removes the 8 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._
# or from a terminal, under your own account: gh repo fork bhaskargurram-ai/unwind --clone && cd unwind curl -s https://killerskills.ai/skills/pypi/rollback-mcp/0.2.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.2.0 && git commit -am "rollback-mcp: Collapsed <details> block carrying instructions" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/rollback-mcp/0.2.0/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.