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. 76 · Caution

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 5 caught lines

Download .patch

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -83,1 +83,0 @@
-<summary>Prefer to create a key by hand?</summary> 1. Open **[thrixel.com/create/#settings/api-keys](https://thrixel.com/create/#settings/api-keys)**. 2. Click 
@@ -123,1 +122,0 @@
-<summary>Passing the key explicitly instead (and why it is second choice)</summary> > **This puts a live key into your shell history** (`~/.bash_history`, > Pow
@@ -269,1 +267,0 @@
-<summary><b>Pre-release / unpublished builds</b></summary> `uvx` can run straight from the repository, no PyPI release needed: ```bash # latest main, ahead of t
diff --git a/thrixel_mcp/credentials.py b/thrixel_mcp/credentials.py
--- a/thrixel_mcp/credentials.py
+++ b/thrixel_mcp/credentials.py
@@ -13,1 +13,0 @@
-in a 0700 directory is what `~/.aws/credentials`, `~/.npmrc`,
@@ -14,1 +13,0 @@
-`~/.docker/config.json` and gh's own fallback do, and it works everywhere.

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.3.37. 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: thrixel-mcp: Collapsed <details> block carrying instructions (KillerSkills verdict caution 76)

## 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 76/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/thrixel-mcp/1.3.37

## Findings with a location
- `README.md:123` · Collapsed <details> block carrying instructions — README.md:123 · Collapsed <details> block carrying instructions
- `README.md:83` · Collapsed <details> block carrying instructions — README.md:83 · Collapsed <details> block carrying instructions
- `thrixel_mcp/credentials.py:13` · References a credential file in the home directory — thrixel_mcp/credentials.py:13 · References a credential file in the home directory
- `thrixel_mcp/credentials.py:14` · References a credential file in the home directory — thrixel_mcp/credentials.py:14 · References a credential file in the home directory
- `README.md:269` · Collapsed <details> block carrying instructions — README.md:269 · 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._

Open the issue on GitHub (thrixel/thrixel_mcp)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork thrixel/thrixel_mcp --clone && cd thrixel_mcp
curl -s https://killerskills.ai/skills/pypi/thrixel-mcp/1.3.37/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.3.37 && git commit -am "thrixel-mcp: Collapsed <details> block carrying instructions"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/thrixel-mcp/1.3.37/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.