Propose a patch

Evidence

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

diff --git a/dist/dist-TRMPOPRZ.js b/dist/dist-TRMPOPRZ.js
--- a/dist/dist-TRMPOPRZ.js
+++ b/dist/dist-TRMPOPRZ.js
@@ -19,1 +19,0 @@
-${h}`,m++;break;case"id":h.includes("\0")||(l=h);break;case"retry":/^\d+$/.test(h)?s(parseInt(h,10)):r(new Dr(`Invalid \`retry\` value: "${h}"`,{type:"invalid-retry",value:h,line:p}));break;default:r(

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 5.0.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: cli: Base64 encoding combined with network call (KillerSkills verdict caution 65)

## 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 65/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/cli/5.0.0

## Findings with a location
- `dist/dist-TRMPOPRZ.js:19` · Base64 encoding combined with network call — dist/dist-TRMPOPRZ.js:19 · Base64 encoding combined with network call — potential data exfiltration

## 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._