Propose a patch

Evidence

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

diff --git a/src/utility_server/dashboard/health.py b/src/utility_server/dashboard/health.py
--- a/src/utility_server/dashboard/health.py
+++ b/src/utility_server/dashboard/health.py
@@ -73,1 +73,0 @@
-kubeconfig = os.environ.get("KUBECONFIG") or os.path.expanduser("~/.kube/config")
diff --git a/src/utility_server/dashboard/app.py b/src/utility_server/dashboard/app.py
--- a/src/utility_server/dashboard/app.py
+++ b/src/utility_server/dashboard/app.py
@@ -89,1 +89,0 @@
-kubeconfig = os.environ.get("KUBECONFIG") or os.path.expanduser("~/.kube/config")
diff --git a/src/utility_server/dashboard/identities.py b/src/utility_server/dashboard/identities.py
--- a/src/utility_server/dashboard/identities.py
+++ b/src/utility_server/dashboard/identities.py
@@ -28,1 +28,0 @@
-kubeconfig = os.environ.get("KUBECONFIG") or os.path.expanduser("~/.kube/config")
diff --git a/src/utility_server/mcp_server.py b/src/utility_server/mcp_server.py
--- a/src/utility_server/mcp_server.py
+++ b/src/utility_server/mcp_server.py
@@ -319,1 +319,0 @@
-return os.environ.get("KUBECONFIG") or os.path.expanduser("~/.kube/config")

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

## 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 78/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-k8s-utility/0.5.0

## Findings with a location
- `src/utility_server/dashboard/health.py:73` · References a credential file in the home directory — src/utility_server/dashboard/health.py:73 · References a credential file in the home directory
- `src/utility_server/dashboard/app.py:89` · References a credential file in the home directory — src/utility_server/dashboard/app.py:89 · References a credential file in the home directory
- `src/utility_server/dashboard/identities.py:28` · References a credential file in the home directory — src/utility_server/dashboard/identities.py:28 · References a credential file in the home directory
- `src/utility_server/mcp_server.py:319` · References a credential file in the home directory — src/utility_server/mcp_server.py:319 · References a credential file in the home directory

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