Propose a patch

Evidence

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

diff --git a/cli/commands/server.sh b/cli/commands/server.sh
--- a/cli/commands/server.sh
+++ b/cli/commands/server.sh
@@ -43,1 +43,0 @@
-prompt_input "SSH key path" "$HOME/.ssh/id_rsa" "auth_value"
diff --git a/cli/lib/menu.sh b/cli/lib/menu.sh
--- a/cli/lib/menu.sh
+++ b/cli/lib/menu.sh
@@ -149,1 +149,0 @@
-echo "  • ~/.ssh/id_rsa (default RSA key)"
@@ -150,1 +149,0 @@
-echo "  • ~/.ssh/id_ed25519 (modern ED25519 key)"
@@ -152,1 +150,0 @@
-prompt_input "SSH key path" "$HOME/.ssh/id_rsa" "auth_value"
@@ -309,1 +306,0 @@
-prompt_input "SSH key path" "${current_keypath:-$HOME/.ssh/id_rsa}" "auth_value"
diff --git a/src/tool-config-manager.js b/src/tool-config-manager.js
--- a/src/tool-config-manager.js
+++ b/src/tool-config-manager.js
@@ -16,1 +16,0 @@
-* User-global only: ~/.ssh-manager/tools-config.json

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 3.1.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: mcp-ssh-manager: References a credential file in the home directory (KillerSkills verdict caution 70)

## 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 70/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/mcp-ssh-manager/3.1.0

## Findings with a location
- `cli/commands/server.sh:43` · References a credential file in the home directory — cli/commands/server.sh:43 · References a credential file in the home directory
- `cli/lib/menu.sh:149` · References a credential file in the home directory — cli/lib/menu.sh:149 · References a credential file in the home directory
- `src/tool-config-manager.js:16` · Reads credential paths from the home directory — src/tool-config-manager.js:16 · Reads credential paths from the home directory
- `cli/lib/menu.sh:309` · References a credential file in the home directory — cli/lib/menu.sh:309 · References a credential file in the home directory
- `cli/lib/menu.sh:150` · References a credential file in the home directory — cli/lib/menu.sh:150 · References a credential file in the home directory
- `cli/lib/menu.sh:152` · References a credential file in the home directory — cli/lib/menu.sh:152 · References a credential file in the home directory

## 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._