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. 65 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 6 caught lines
Download .patchdiff --git a/README.md b/README.md --- a/README.md +++ b/README.md @@ -229,1 +229,0 @@ -<summary><b>Installer options</b></summary> | macOS | Windows | Effect | |---|---|---| | `--model all` | `-Model all` | Also download the small, fast `sm-music` @@ -256,1 +255,0 @@ -<summary><b>Parameter notes</b></summary> - **`audio_type`**: `music` / `instrument` / `sfx` / `raw`. The server adds the prefix the model was trained with (`Tr @@ -322,1 +320,0 @@ -<summary><b>Share one server between sessions</b></summary> Each client session normally starts its own server process. Models load on the first call and are fr @@ -380,1 +377,0 @@ -<summary><b>Does it run on Windows, Linux or Intel Macs?</b></summary> **Windows:** yes, with an NVIDIA GPU. See [Quick start](#-quick-start). **Linux:** with a @@ -390,1 +386,0 @@ -<summary><b>"Intel Macs are not supported" on an Apple Silicon Mac?</b></summary> The environment was built with an x86_64 Python (for example an old Intel Home diff --git a/src/audio_studio_mcp/weights.py b/src/audio_studio_mcp/weights.py --- a/src/audio_studio_mcp/weights.py +++ b/src/audio_studio_mcp/weights.py @@ -140,1 +140,0 @@ -" own terminal (not in a chat), run this and paste the token:\n"
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.1.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: audio-studio-mcp: Collapsed <details> block carrying instructions (KillerSkills verdict caution 65)
## 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 65/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/audio-studio-mcp/1.1.1 ## Findings with a location - `README.md:390` · Collapsed <details> block carrying instructions — README.md:390 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file - `README.md:256` · Collapsed <details> block carrying instructions — README.md:256 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file - `src/audio_studio_mcp/weights.py:140` · Prompting user to enter sensitive credentials — src/audio_studio_mcp/weights.py:140 · Prompting user to enter sensitive credentials — social engineering - `README.md:322` · Collapsed <details> block carrying instructions — README.md:322 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file - `README.md:380` · Collapsed <details> block carrying instructions — README.md:380 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file - `README.md:229` · Collapsed <details> block carrying instructions — README.md:229 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file ## 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._
# or from a terminal, under your own account: gh repo fork kanaworksai-hue/audio-studio-mcp --clone && cd audio-studio-mcp curl -s https://killerskills.ai/skills/pypi/audio-studio-mcp/1.1.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.1.1 && git commit -am "audio-studio-mcp: Collapsed <details> block carrying instructions" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/audio-studio-mcp/1.1.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.