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. 73 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 3 caught lines
Download .patchdiff --git a/README.md b/README.md --- a/README.md +++ b/README.md @@ -275,1 +275,0 @@ -<summary><b>serena</b> — a PyPI server behind a subcommand (<code>serena-agent</code>)</summary> <br> [Serena](https://github.com/oraios/serena) exposes its MCP @@ -331,1 +330,0 @@ -<summary><b>fetch</b> — an official PyPI server, no overrides (<code>mcp-server-fetch</code>)</summary> <br> The reference [fetch](https://github.com/modelconte @@ -355,1 +353,0 @@ -<summary><b>serena via <code>.mcpb.toml</code></b> — keep the recipe in a config file</summary> <br> Drop a `.mcpb.toml` in the directory you run the converter
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.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: mcp2mcpb: Collapsed <details> block carrying instructions (KillerSkills verdict caution 73)
## 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 73/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/mcp2mcpb/1.0.0 ## Findings with a location - `README.md:331` · Collapsed <details> block carrying instructions — README.md:331 · Collapsed <details> block carrying instructions - `README.md:275` · Collapsed <details> block carrying instructions — README.md:275 · Collapsed <details> block carrying instructions - `README.md:355` · Collapsed <details> block carrying instructions — README.md:355 · Collapsed <details> block carrying instructions ## Proposed change The attached patch removes the 3 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 Anselmoo/mcp2mcpb --clone && cd mcp2mcpb curl -s https://killerskills.ai/skills/pypi/mcp2mcpb/1.0.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.0 && git commit -am "mcp2mcpb: Collapsed <details> block carrying instructions" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/mcp2mcpb/1.0.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.