Propose a patch

Evidence

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

diff --git a/tests/conftest.py b/tests/conftest.py
--- a/tests/conftest.py
+++ b/tests/conftest.py
@@ -33,1 +33,0 @@
-"ssh_key_path": "~/.ssh/id_ed25519",
@@ -47,1 +46,0 @@
-"ssh_key_path": "~/.ssh/id_ed25519",
@@ -62,1 +60,0 @@
-"SSH_KEY_PATH": "~/.ssh/id_ed25519",
diff --git a/mcp_homelab/cli.py b/mcp_homelab/cli.py
--- a/mcp_homelab/cli.py
+++ b/mcp_homelab/cli.py
@@ -36,1 +36,0 @@
-#   ssh_key_path: "~/.ssh/id_ed25519"
diff --git a/mcp_homelab/setup/node_setup.py b/mcp_homelab/setup/node_setup.py
--- a/mcp_homelab/setup/node_setup.py
+++ b/mcp_homelab/setup/node_setup.py
@@ -88,1 +88,0 @@
-ssh_key_path = prompt_path("SSH key path", default="~/.ssh/id_ed25519")
diff --git a/tests/unit/test_config.py b/tests/unit/test_config.py
--- a/tests/unit/test_config.py
+++ b/tests/unit/test_config.py
@@ -65,1 +65,0 @@
-ssh_key_path="~/.ssh/id_ed25519",
@@ -267,1 +266,0 @@
-"ssh_key_path": "~/.ssh/id_ed25519",
diff --git a/tests/unit/test_ssh.py b/tests/unit/test_ssh.py
--- a/tests/unit/test_ssh.py
+++ b/tests/unit/test_ssh.py
@@ -33,1 +33,0 @@
-ssh_key_path="~/.ssh/id_ed25519",
@@ -83,1 +82,0 @@
-key_filename=str(Path("~/.ssh/id_ed25519").expanduser()),
diff --git a/tests/unit/test_install.py b/tests/unit/test_install.py
--- a/tests/unit/test_install.py
+++ b/tests/unit/test_install.py
@@ -431,1 +431,0 @@
-env_file.write_text("SSH_USER=admin\nSSH_KEY_PATH=~/.ssh/id_ed25519\n", encoding="utf-8")

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.4.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: mcp-homelab: 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/pypi/mcp-homelab/1.4.1

## Findings with a location
- `tests/conftest.py:47` · References a credential file in the home directory — tests/conftest.py:47 · References a credential file in the home directory
- `mcp_homelab/cli.py:36` · References a credential file in the home directory — mcp_homelab/cli.py:36 · References a credential file in the home directory
- `mcp_homelab/setup/node_setup.py:88` · References a credential file in the home directory — mcp_homelab/setup/node_setup.py:88 · References a credential file in the home directory
- `tests/conftest.py:62` · References a credential file in the home directory — tests/conftest.py:62 · References a credential file in the home directory
- `tests/conftest.py:33` · References a credential file in the home directory — tests/conftest.py:33 · References a credential file in the home directory
- `tests/unit/test_config.py:65` · References a credential file in the home directory — tests/unit/test_config.py:65 · References a credential file in the home directory
- `tests/unit/test_config.py:267` · References a credential file in the home directory — tests/unit/test_config.py:267 · References a credential file in the home directory
- `tests/unit/test_ssh.py:33` · References a credential file in the home directory — tests/unit/test_ssh.py:33 · References a credential file in the home directory
- `tests/unit/test_install.py:431` · References a credential file in the home directory — tests/unit/test_install.py:431 · References a credential file in the home directory
- `tests/unit/test_ssh.py:83` · References a credential file in the home directory — tests/unit/test_ssh.py:83 · References a credential file in the home directory

## Proposed change
The attached patch removes the 10 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._