Propose a patch

Evidence

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

diff --git a/lib/utils/proxy.js b/lib/utils/proxy.js
--- a/lib/utils/proxy.js
+++ b/lib/utils/proxy.js
@@ -18,1 +18,0 @@
-* 安​全：代理 URL 的 userinfo（账号/密码）只用于 `Proxy-Authorization` 头，绝不进日志；
@@ -51,1 +50,0 @@
-/** 读代理环境变量（纯函数，便于测试注​入任意 env） */
diff --git a/src/utils/proxy.ts b/src/utils/proxy.ts
--- a/src/utils/proxy.ts
+++ b/src/utils/proxy.ts
@@ -18,1 +18,0 @@
-* 安​全：代理 URL 的 userinfo（账号/密码）只用于 `Proxy-Authorization` 头，绝不进日志；
@@ -67,1 +66,0 @@
-/** 读代理环境变量（纯函数，便于测试注​入任意 env） */

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.4.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: dsh-config-manager: 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.8.1) 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/npm/dsh-config-manager/0.4.3

## Findings with a location
- `lib/utils/proxy.js:18` · Hidden zero-width characters detected — lib/utils/proxy.js:18 · Hidden zero-width characters detected — may conceal content
- `src/utils/proxy.ts:67` · Hidden zero-width characters detected — src/utils/proxy.ts:67 · Hidden zero-width characters detected — may conceal content
- `src/utils/proxy.ts:18` · Hidden zero-width characters detected — src/utils/proxy.ts:18 · Hidden zero-width characters detected — may conceal content
- `lib/utils/proxy.js:51` · Hidden zero-width characters detected — lib/utils/proxy.js:51 · Hidden zero-width characters detected — may conceal content

## Proposed change
The attached patch removes the 4 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._