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. 71 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 5 caught lines
Download .patchdiff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -571,1 +571,0 @@
-<summary><b>Claude Desktop</b> — <code>claude_desktop_config.json</code></summary> macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` Wind
@@ -593,1 +592,0 @@
-<summary><b>Cursor</b> — <code>.cursor/mcp.json</code></summary> Project-local (`.cursor/mcp.json`) or global (`~/.cursor/mcp.json`): ```json { "mcpServers": {
@@ -611,1 +609,0 @@
-<summary><b>VS Code</b> — <code>.vscode/mcp.json</code></summary> ```json { "servers": { "legacy2mcp": { "type": "stdio", "command": "uvx", "args": ["legacy2mcp
@@ -628,1 +625,0 @@
-<summary><b>Claude Code</b> — CLI</summary> ```bash claude mcp add legacy2mcp -- uvx legacy2mcp run --config /absolute/path/to/config.yaml ``` Add `--scope proj
@@ -640,1 +636,0 @@
-<summary><b>MCP Inspector</b> — a validation tool, not an AI client</summary> ```bash npx @modelcontextprotocol/inspector uvx legacy2mcp run --config /absolute/
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.5.1. 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: legacy2mcp: Collapsed <details> block carrying instructions (KillerSkills verdict caution 71)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.6) and scored it **CAUTION 71/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/pypi/legacy2mcp/0.5.1 ## Findings with a location - `README.md:640` · Collapsed <details> block carrying instructions — README.md:640 · Collapsed <details> block carrying instructions - `README.md:571` · Collapsed <details> block carrying instructions — README.md:571 · Collapsed <details> block carrying instructions - `README.md:628` · Collapsed <details> block carrying instructions — README.md:628 · Collapsed <details> block carrying instructions - `README.md:611` · Collapsed <details> block carrying instructions — README.md:611 · Collapsed <details> block carrying instructions - `README.md:593` · Collapsed <details> block carrying instructions — README.md:593 · Collapsed <details> block carrying instructions ## Proposed change The attached patch removes the 5 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 bvenkata/legacy2mcp --clone && cd legacy2mcp curl -s https://killerskills.ai/skills/pypi/legacy2mcp/0.5.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.5.1 && git commit -am "legacy2mcp: Collapsed <details> block carrying instructions" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/legacy2mcp/0.5.1/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.