Propose a patch

Evidence

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

diff --git a/src/yaml_lite.py b/src/yaml_lite.py
--- a/src/yaml_lite.py
+++ b/src/yaml_lite.py
@@ -762,1 +762,0 @@
-if text.startswith(""):
diff --git a/tests/test_redactor.py b/tests/test_redactor.py
--- a/tests/test_redactor.py
+++ b/tests/test_redactor.py
@@ -27,1 +27,0 @@
-("url_credentials", "clone https://deploy:[email protected]/repo.git", "gh0stPass"),

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.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: kubeguard-mcp: Hidden zero-width characters detected (KillerSkills verdict caution 63)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 63/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/kubeguard-mcp/1.0.0

## Findings with a location
- `src/yaml_lite.py:762` · Hidden zero-width characters detected — src/yaml_lite.py:762 · Hidden zero-width characters detected — may conceal content
- `tests/test_redactor.py:27` · URL with embedded credentials — tests/test_redactor.py:27 · URL with embedded credentials — may be phishing or credential leaking

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