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 3 caught lines
Download .patchdiff --git a/README.md b/README.md --- a/README.md +++ b/README.md @@ -191,1 +191,0 @@ -<summary><b>Prefer ReaPack for the REAPER side?</b></summary> In REAPER: **Extensions → ReaPack → Import repositories…**, paste `https://github.com/mthines/reap @@ -236,1 +235,0 @@ -<summary><b>Something not working?</b></summary> <br> - **Run `reaper-mcp doctor`.** It checks the bridge, whether it starts with REAPER, the skills and the Cla @@ -620,1 +618,0 @@ -<summary><b>Can it wreck my project?</b></summary> <br> Every edit is a single undo step, and the mix skills snapshot before and after a task. Use <code>/critiq
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.99.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: reaper-mcp: Collapsed <details> block carrying instructions (KillerSkills verdict caution 78)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) 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/npm/reaper-mcp/0.99.0 ## Findings with a location - `README.md:191` · Collapsed <details> block carrying instructions — README.md:191 · Collapsed <details> block carrying instructions - `README.md:620` · Collapsed <details> block carrying instructions — README.md:620 · Collapsed <details> block carrying instructions - `README.md:236` · Collapsed <details> block carrying instructions — README.md:236 · 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 mthines/reaper-mcp --clone && cd reaper-mcp curl -s https://killerskills.ai/skills/npm/reaper-mcp/0.99.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.99.0 && git commit -am "reaper-mcp: Collapsed <details> block carrying instructions" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/reaper-mcp/0.99.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.