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. 61 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 3 caught lines
Download .patchdiff --git a/src/logic_analyzer_mcp/mcp_tools_experimental.py b/src/logic_analyzer_mcp/mcp_tools_experimental.py --- a/src/logic_analyzer_mcp/mcp_tools_experimental.py +++ b/src/logic_analyzer_mcp/mcp_tools_experimental.py @@ -1,1 +1,0 @@ -from mcp.server.fastmcp import FastMCP, Context diff --git a/src/logic_analyzer_mcp/server.py b/src/logic_analyzer_mcp/server.py --- a/src/logic_analyzer_mcp/server.py +++ b/src/logic_analyzer_mcp/server.py @@ -1,1 +1,0 @@ -import logging diff --git a/src/logic_analyzer_mcp/controllers/logic2_automation_controller.py b/src/logic_analyzer_mcp/controllers/logic2_automation_controller.py --- a/src/logic_analyzer_mcp/controllers/logic2_automation_controller.py +++ b/src/logic_analyzer_mcp/controllers/logic2_automation_controller.py @@ -1,1 +1,0 @@ -from typing import List, Optional, Dict, Any
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.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: logic-analyzer-mcp: Hidden zero-width characters detected (KillerSkills verdict caution 61)
## 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 61/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/pypi/logic-analyzer-mcp/0.1.0 ## Findings with a location - `src/logic_analyzer_mcp/mcp_tools_experimental.py:1` · Hidden zero-width characters detected — src/logic_analyzer_mcp/mcp_tools_experimental.py:1 · Hidden zero-width characters detected — may conceal content - `src/logic_analyzer_mcp/server.py:1` · Hidden zero-width characters detected — src/logic_analyzer_mcp/server.py:1 · Hidden zero-width characters detected — may conceal content - `src/logic_analyzer_mcp/controllers/logic2_automation_controller.py:1` · Hidden zero-width characters detected — src/logic_analyzer_mcp/controllers/logic2_automation_controller.py:1 · Hidden zero-width characters detected — may conceal content ## Proposed change The attached patch removes the 3 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 michelebergo/logic-analyzer-ai-mcp --clone && cd logic-analyzer-ai-mcp curl -s https://killerskills.ai/skills/pypi/logic-analyzer-mcp/0.1.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.1.0 && git commit -am "logic-analyzer-mcp: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/logic-analyzer-mcp/0.1.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.