Propose a patch

Evidence

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

diff --git a/src/mcp_audit/checks/ts_dns_rebinding.py b/src/mcp_audit/checks/ts_dns_rebinding.py
--- a/src/mcp_audit/checks/ts_dns_rebinding.py
+++ b/src/mcp_audit/checks/ts_dns_rebinding.py
@@ -349,1 +349,0 @@
-_WS_CHARS = " \t\r\n\v\f "
diff --git a/tests/test_ts_destructive_fs_sink.py b/tests/test_ts_destructive_fs_sink.py
--- a/tests/test_ts_destructive_fs_sink.py
+++ b/tests/test_ts_destructive_fs_sink.py
@@ -371,1 +371,0 @@
-(bom / "server.ts").write_text("" + HDR + body, encoding="utf-8")

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

## 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 69/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/mcpdone-audit/0.11.3

## Findings with a location
- `src/mcp_audit/checks/ts_dns_rebinding.py:349` · Hidden zero-width characters detected — src/mcp_audit/checks/ts_dns_rebinding.py:349 · Hidden zero-width characters detected — may conceal content
- `tests/test_ts_destructive_fs_sink.py:371` · Hidden zero-width characters detected — tests/test_ts_destructive_fs_sink.py:371 · Hidden zero-width characters detected — may conceal content

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