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. 73 · Caution

Evidence

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

Diff · removes 2 caught lines

Download .patch

diff --git a/tg_mcp/common.py b/tg_mcp/common.py
--- a/tg_mcp/common.py
+++ b/tg_mcp/common.py
@@ -649,1 +649,0 @@
-G·em·i‌n‍i  ‌Pr‌o        （中间夹着 U+200C / U+200D / U+1808 和「·」）
diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md
--- a/.github/ISSUE_TEMPLATE/bug.md
+++ b/.github/ISSUE_TEMPLATE/bug.md
@@ -11,1 +11,0 @@
-Paste the error text or the wrong part of the JSON. Never paste your .env or session string. / 贴报错原文或结果里不对的那段。千万别贴 .env 和登录凭证。

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: sherlogram: Hidden zero-width characters detected (KillerSkills verdict caution 73)

## 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 73/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/sherlogram/1.0.0

## Findings with a location
- `tg_mcp/common.py:649` · Hidden zero-width characters detected — tg_mcp/common.py:649 · Hidden zero-width characters detected — may conceal content
- `.github/ISSUE_TEMPLATE/bug.md:11` · HTML comment carrying imperative instructions to the agent — .github/ISSUE_TEMPLATE/bug.md:11 · HTML comment carrying imperative instructions to the agent · informational: not an instruction file

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

Open the issue on GitHub (jackchen175x/sherlogram)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork jackchen175x/sherlogram --clone && cd sherlogram
curl -s https://killerskills.ai/skills/glama/sherlogram/1.0.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.0.0 && git commit -am "sherlogram: Hidden zero-width characters detected"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/sherlogram/1.0.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.