← steward-mcp@0.1.1

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

Evidence

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

Diff · removes 6 caught lines

Download .patch
diff --git a/src/assistant/toolsets.py b/src/assistant/toolsets.py
--- a/src/assistant/toolsets.py
+++ b/src/assistant/toolsets.py
@@ -131,1 +131,0 @@
-"ایمیل‌ها",
@@ -132,1 +131,0 @@
-"ایمیل‌هایم",
@@ -135,1 +133,0 @@
-"نامه‌ها",
@@ -137,1 +134,0 @@
-"پیام‌ها",
@@ -157,1 +153,0 @@
-"پیام‌ها",
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -804,1 +804,0 @@
-| `/schedules` · `/schedule add <name> <daily HH:MM\|weekdays HH:MM\|every Nh> <prompt>` | Recurring prompts, e.g. a morning briefing; also `pause` / `resume` / `remove` |

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

## 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 68/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/steward-mcp/0.1.1

## Findings with a location
- `src/assistant/toolsets.py:131` · Hidden zero-width characters detected — src/assistant/toolsets.py:131 · Hidden zero-width characters detected — may conceal content
- `src/assistant/toolsets.py:135` · Hidden zero-width characters detected — src/assistant/toolsets.py:135 · Hidden zero-width characters detected — may conceal content
- `src/assistant/toolsets.py:132` · Hidden zero-width characters detected — src/assistant/toolsets.py:132 · Hidden zero-width characters detected — may conceal content
- `src/assistant/toolsets.py:157` · Hidden zero-width characters detected — src/assistant/toolsets.py:157 · Hidden zero-width characters detected — may conceal content
- `src/assistant/toolsets.py:137` · Hidden zero-width characters detected — src/assistant/toolsets.py:137 · Hidden zero-width characters detected — may conceal content
- `README.md:804` · Fake instruction boundary tag — README.md:804 · Fake instruction boundary tag · informational: not an instruction file

## Proposed change
The attached patch removes the 6 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 navid72m/vps-mcp --clone && cd vps-mcp
curl -s https://killerskills.ai/skills/pypi/steward-mcp/0.1.1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.1.1 && git commit -am "steward-mcp: Hidden zero-width characters detected"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/steward-mcp/0.1.1/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.