Propose a patch

Evidence

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

diff --git a/src/svg_mcp/_ext_apps_inline.js b/src/svg_mcp/_ext_apps_inline.js
--- a/src/svg_mcp/_ext_apps_inline.js
+++ b/src/svg_mcp/_ext_apps_inline.js
@@ -38,1 +38,0 @@
-…ted,t=k(n.input),o=u[t]??t;if(/^[A-Z]/.test(n.expected))return`ورودی نامعتبر: می‌بایست instanceof ${n.expected} می‌بود، ${o} دریافت شد`;return`ورودی نامعتبر: می‌…

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

## 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 74/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/svg-mcp/0.10.4

## Findings with a location
- `src/svg_mcp/_ext_apps_inline.js:38` · Hidden zero-width characters detected — src/svg_mcp/_ext_apps_inline.js:38 · Hidden zero-width characters detected — may conceal content

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