← modsearch-plus@5.11.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. 59 · Caution

Evidence

  • Read ~/.npmrc in the decoy home directory.

Diff · removes 3 caught lines

Download .patch
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -68,1 +68,0 @@
-<summary>DeepSeek Harness (recommended)</summary> ```sh npx -y @deepseek-ai/dsh plugin --profile web add [email protected] ``` In the desktop app, enter `mo
@@ -103,1 +102,0 @@
-<summary>Settings card</summary> In the DeepSeek Harness settings card you pick a preferred engine, enter API keys, set a self-hosted endpoint, and tick the eng
diff --git a/README.zh-CN.md b/README.zh-CN.md
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -103,1 +103,0 @@
-<summary>设置卡片</summary> 在 DeepSeek Harness 设置卡片中选择首选引擎、填入 API key、配置自托管端点、勾选参与故障转移的引擎。保存即生效;已保存的 key 不会发送到浏览器。

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 5.11.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: modsearch-plus: Read ~/.npmrc in the decoy home directory (KillerSkills verdict caution 59)

## 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 59/100**. Summary: reads credential files.

- Read ~/.npmrc in the decoy home directory.

Full trace and findings: https://killerskills.ai/skills/npm/modsearch-plus/5.11.0

## Findings with a location
- `README.md:103` · Collapsed <details> block carrying instructions — README.md:103 · Collapsed <details> block carrying instructions
- `README.zh-CN.md:103` · Collapsed <details> block carrying instructions — README.zh-CN.md:103 · Collapsed <details> block carrying instructions
- `README.md:68` · Collapsed <details> block carrying instructions — README.md:68 · Collapsed <details> block carrying instructions

## 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 ciskonc/modsearch-plus --clone && cd modsearch-plus
curl -s https://killerskills.ai/skills/npm/modsearch-plus/5.11.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/5.11.0 && git commit -am "modsearch-plus: Read ~/.npmrc in the decoy home directory"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/modsearch-plus/5.11.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.