← mseep-trendradar-mcp@1.0.3

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

Evidence

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

Diff · removes 6 caught lines

Download .patch
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -1075,1 +1075,0 @@
-<summary>👉 点击展开：<strong>Telegram Bot</strong></summary> <br> **GitHub Secret 配置（⚠️ Name 名称必须严格一致）：** - **Name（名称）**：`TELEGRAM_BOT_TOKEN`（请复制粘贴此名称，不要手打） - **Sec
@@ -1319,1 +1318,0 @@
-<summary>👉 点击展开：<strong>Bark 推送</strong>（iOS 专属，简洁高效）</summary> <br> **GitHub Secret 配置（⚠️ Name 名称必须严格一致）：** - **Name（名称）**：`BARK_URL`（请复制粘贴此名称，不要手打） - **Secre
diff --git a/README-EN.md b/README-EN.md
--- a/README-EN.md
+++ b/README-EN.md
@@ -1517,1 +1517,0 @@
-<summary>👉 Click to expand: <strong>Custom Monitoring Platforms</strong></summary> <br> **Configuration Location:** `platforms` section in `config/config.yaml`
@@ -2639,1 +2638,0 @@
-<summary><strong>Telegram Paired Configuration</strong></summary> ```bash # ✅ Correct: 2 tokens correspond to 2 chat_ids TELEGRAM_BOT_TOKEN=123456:AAA-BBB;78901
@@ -2656,1 +2654,0 @@
-<summary><strong>ntfy Paired Configuration</strong></summary> ```bash # ✅ Correct: 3 topics, only the 2nd needs a token NTFY_TOPIC=topic1;topic2;topic3 NTFY_TOK
@@ -2708,1 +2705,0 @@
-<summary><strong>Telegram Paired Configuration</strong></summary> ```bash # ✅ Correct: 2 tokens correspond to 2 chat_ids TELEGRAM_BOT_TOKEN=123456:AAA-BBB;78901

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.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: mseep-trendradar-mcp: Collapsed <details> block carrying instructions (KillerSkills verdict caution 64)

## 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 64/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/mseep-trendradar-mcp/1.0.3

## Findings with a location
- `README.md:1319` · Collapsed <details> block carrying instructions — README.md:1319 · Collapsed <details> block carrying instructions
- `README-EN.md:2656` · Collapsed <details> block carrying instructions — README-EN.md:2656 · Collapsed <details> block carrying instructions
- `README-EN.md:1517` · Collapsed <details> block carrying instructions — README-EN.md:1517 · Collapsed <details> block carrying instructions
- `README-EN.md:2639` · Collapsed <details> block carrying instructions — README-EN.md:2639 · Collapsed <details> block carrying instructions
- `README.md:1075` · Collapsed <details> block carrying instructions — README.md:1075 · Collapsed <details> block carrying instructions
- `README-EN.md:2708` · Collapsed <details> block carrying instructions — README-EN.md:2708 · Collapsed <details> block carrying instructions

## 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._
Open the issue on GitHub (sansan0/TrendRadar)Fork to open a PR
# or from a terminal, under your own account:
gh repo fork sansan0/TrendRadar --clone && cd TrendRadar
curl -s https://killerskills.ai/skills/pypi/mseep-trendradar-mcp/1.0.3/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.0.3 && git commit -am "mseep-trendradar-mcp: Collapsed <details> block carrying instructions"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/mseep-trendradar-mcp/1.0.3/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.