← verified-googledocs-mcp@0.2.0

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 76 · Caution

Evidence

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

Diff · removes 17 caught lines

Download .patch
diff --git a/scripts/seed_live_fixture.py b/scripts/seed_live_fixture.py
--- a/scripts/seed_live_fixture.py
+++ b/scripts/seed_live_fixture.py
@@ -33,1 +33,0 @@
-#   = NBSP, ­ = soft hyphen. The duplicated fox sentence must appear
@@ -41,1 +40,0 @@
-"Soft hyphen: super­seded\n"
@@ -59,1 +57,0 @@
-"ZWJ emoji sequence: \U0001f468‍\U0001f469‍\U0001f467 "
diff --git a/tests/live/test_reads.py b/tests/live/test_reads.py
--- a/tests/live/test_reads.py
+++ b/tests/live/test_reads.py
@@ -24,1 +24,0 @@
-s = s.replace(" ", " ").replace("­", "")  # NBSP -> space, soft hyphen -> gone
diff --git a/src/verified_googledocs_mcp/verify.py b/src/verified_googledocs_mcp/verify.py
--- a/src/verified_googledocs_mcp/verify.py
+++ b/src/verified_googledocs_mcp/verify.py
@@ -444,1 +444,0 @@
-if ch == "­":
diff --git a/tests/live/test_replace_text.py b/tests/live/test_replace_text.py
--- a/tests/live/test_replace_text.py
+++ b/tests/live/test_replace_text.py
@@ -239,1 +239,0 @@
-assert "👨‍👩‍👧" in after
diff --git a/tests/unit/fixtures/document.json b/tests/unit/fixtures/document.json
--- a/tests/unit/fixtures/document.json
+++ b/tests/unit/fixtures/document.json
@@ -115,1 +115,0 @@
-"content": "Soft hyphen: super­seded\n",
@@ -693,1 +692,0 @@
-"content": "ZWJ emoji sequence: 👨‍👩‍👧 (family: man+ZWJ+woman+ZWJ+girl)\n",
diff --git a/tests/unit/test_locate.py b/tests/unit/test_locate.py
--- a/tests/unit/test_locate.py
+++ b/tests/unit/test_locate.py
@@ -207,1 +207,0 @@
-tab = _tab(["pro­gramming"])
@@ -213,1 +212,0 @@
-result = locate("pro­gramming", tab)
@@ -361,1 +359,0 @@
-# 👨‍💻 is U+1F468 ZWJ U+1F4BB = 2 + 1 (ZWJ is BMP) + 2 = 5 UTF-16 units.
@@ -362,1 +359,0 @@
-zwj_seq = "\U0001f468‍\U0001f4bb"
@@ -479,1 +475,0 @@
-tab = _tab(["pro­gramming"])
diff --git a/tests/unit/test_markdown_writer.py b/tests/unit/test_markdown_writer.py
--- a/tests/unit/test_markdown_writer.py
+++ b/tests/unit/test_markdown_writer.py
@@ -59,1 +59,0 @@
-# 👨‍👩‍👧 is a ZWJ sequence: three emoji + two ZWJs = 3*2 + 2*1 = 8 UTF-16 units.
@@ -60,1 +59,0 @@
-seq = "👨‍👩‍👧"
diff --git a/tests/unit/test_tables.py b/tests/unit/test_tables.py
--- a/tests/unit/test_tables.py
+++ b/tests/unit/test_tables.py
@@ -773,1 +773,0 @@
-("soft­hyphen", "softhyphen"),  # soft hyphen stripped
diff --git a/tests/unit/test_diff_tab_vs_file.py b/tests/unit/test_diff_tab_vs_file.py
--- a/tests/unit/test_diff_tab_vs_file.py
+++ b/tests/unit/test_diff_tab_vs_file.py
@@ -473,1 +473,0 @@
-denylist exists for ("diff against ~/.ssh/id_rsa")."""

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

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 76/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/verified-googledocs-mcp/0.2.0

## Findings with a location
- `scripts/seed_live_fixture.py:41` · Hidden zero-width characters detected — scripts/seed_live_fixture.py:41 · Hidden zero-width characters detected — may conceal content
- `tests/live/test_reads.py:24` · Hidden zero-width characters detected — tests/live/test_reads.py:24 · Hidden zero-width characters detected — may conceal content
- `src/verified_googledocs_mcp/verify.py:444` · Hidden zero-width characters detected — src/verified_googledocs_mcp/verify.py:444 · Hidden zero-width characters detected — may conceal content
- `tests/live/test_replace_text.py:239` · Hidden zero-width characters detected — tests/live/test_replace_text.py:239 · Hidden zero-width characters detected — may conceal content
- `scripts/seed_live_fixture.py:33` · Hidden zero-width characters detected — scripts/seed_live_fixture.py:33 · Hidden zero-width characters detected — may conceal content
- `tests/unit/fixtures/document.json:115` · Hidden zero-width characters detected — tests/unit/fixtures/document.json:115 · Hidden zero-width characters detected — may conceal content
- `scripts/seed_live_fixture.py:59` · Hidden zero-width characters detected — scripts/seed_live_fixture.py:59 · Hidden zero-width characters detected — may conceal content
- `tests/unit/test_locate.py:361` · Hidden zero-width characters detected — tests/unit/test_locate.py:361 · Hidden zero-width characters detected — may conceal content
- `tests/unit/test_locate.py:479` · Hidden zero-width characters detected — tests/unit/test_locate.py:479 · Hidden zero-width characters detected — may conceal content
- `tests/unit/test_locate.py:207` · Hidden zero-width characters detected — tests/unit/test_locate.py:207 · Hidden zero-width characters detected — may conceal content
- `tests/unit/test_markdown_writer.py:60` · Hidden zero-width characters detected — tests/unit/test_markdown_writer.py:60 · Hidden zero-width characters detected — may conceal content
- `tests/unit/test_tables.py:773` · Hidden zero-width characters detected — tests/unit/test_tables.py:773 · Hidden zero-width characters detected — may conceal content

## Proposed change
The attached patch removes the 17 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._
# or from a terminal, under your own account:
gh repo fork michaelrobertsutton/verified-googledocs-mcp --clone && cd verified-googledocs-mcp
curl -s https://killerskills.ai/skills/pypi/verified-googledocs-mcp/0.2.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.2.0 && git commit -am "verified-googledocs-mcp: Hidden zero-width characters detected"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/verified-googledocs-mcp/0.2.0/patch.md)

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.