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. 68 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 7 caught lines
Download .patchdiff --git a/termux_mcp/smart/fixgraph.py b/termux_mcp/smart/fixgraph.py
--- a/termux_mcp/smart/fixgraph.py
+++ b/termux_mcp/smart/fixgraph.py
@@ -78,1 +78,0 @@
-("git_auth_ssh", "E_GIT_AUTH", r"publickey", ["test -f ~/.ssh/id_ed25519 || ssh-keygen -t ed25519 -N '' -f ~/.ssh/id_ed25519",
@@ -79,1 +78,0 @@
-"cat ~/.ssh/id_ed25519.pub"], "", "write",
diff --git a/termux_mcp/handlers/ai_power.py b/termux_mcp/handlers/ai_power.py
--- a/termux_mcp/handlers/ai_power.py
+++ b/termux_mcp/handlers/ai_power.py
@@ -274,1 +274,0 @@
-'if [ -f ~/.ssh/id_rsa ]; then echo " ✅ RSA key exists ($(wc -c < ~/.ssh/id_rsa.pub) bytes)"; else '
@@ -275,1 +274,0 @@
-'echo " Generating RSA key..."; ssh-keygen -t rsa -b 4096 -f ~/.ssh/id_rsa -N "" -q && echo " ✅ Key generated"; fi',
@@ -286,1 +284,0 @@
-'cat ~/.ssh/id_rsa.pub 2>/dev/null || echo "No public key"',
@@ -301,1 +298,0 @@
-'ssh-keygen -lf ~/.ssh/id_rsa.pub 2>/dev/null || echo "No key"',
diff --git a/termux_mcp/checks/ssh_keys_present.json b/termux_mcp/checks/ssh_keys_present.json
--- a/termux_mcp/checks/ssh_keys_present.json
+++ b/termux_mcp/checks/ssh_keys_present.json
@@ -6,1 +6,0 @@
-"probe": "test -f ~/.ssh/id_ed25519.pub || test -f ~/.ssh/id_rsa.pub || test -f ~/.ssh/id_ecdsa.pub",
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.15.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: termux-mcp: References a credential file in the home directory (KillerSkills verdict caution 68)
## 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 68/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/termux-mcp/0.15.0 ## Findings with a location - `termux_mcp/smart/fixgraph.py:78` · References a credential file in the home directory — termux_mcp/smart/fixgraph.py:78 · References a credential file in the home directory - `termux_mcp/smart/fixgraph.py:79` · Reads credential paths from the home directory — termux_mcp/smart/fixgraph.py:79 · Reads credential paths from the home directory - `termux_mcp/handlers/ai_power.py:275` · References a credential file in the home directory — termux_mcp/handlers/ai_power.py:275 · References a credential file in the home directory - `termux_mcp/handlers/ai_power.py:301` · References a credential file in the home directory — termux_mcp/handlers/ai_power.py:301 · References a credential file in the home directory - `termux_mcp/checks/ssh_keys_present.json:6` · References a credential file in the home directory — termux_mcp/checks/ssh_keys_present.json:6 · References a credential file in the home directory - `termux_mcp/handlers/ai_power.py:274` · References a credential file in the home directory — termux_mcp/handlers/ai_power.py:274 · References a credential file in the home directory - `termux_mcp/smart/fixgraph.py:79` · References a credential file in the home directory — termux_mcp/smart/fixgraph.py:79 · References a credential file in the home directory - `termux_mcp/handlers/ai_power.py:286` · References a credential file in the home directory — termux_mcp/handlers/ai_power.py:286 · References a credential file in the home directory - `termux_mcp/handlers/ai_power.py:286` · Reads credential paths from the home directory — termux_mcp/handlers/ai_power.py:286 · Reads credential paths from the home directory ## Proposed change The attached patch removes the 7 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 termuxgpt/termux-mcp --clone && cd termux-mcp curl -s https://killerskills.ai/skills/pypi/termux-mcp/0.15.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.15.0 && git commit -am "termux-mcp: References a credential file in the home directory" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/termux-mcp/0.15.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.