Propose a patch

Evidence

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

diff --git a/dist/index.mjs b/dist/index.mjs
--- a/dist/index.mjs
+++ b/dist/index.mjs
@@ -52,1 +52,0 @@
-`);throw console.error(`${q} Build failed for "${e}" (with hooks): ${n}`),new X(e,n,{cause:Error(n)})}return{outputPath:o,cleanup:()=>this.safeUnlink(o)}}catch(t){if(t instanceof X)throw t;let n=t ins
diff --git a/dist/index.cjs b/dist/index.cjs
--- a/dist/index.cjs
+++ b/dist/index.cjs
@@ -52,1 +52,0 @@
-`);throw console.error(`${G} Build failed for "${e}" (with hooks): ${n}`),new J(e,n,{cause:Error(n)})}return{outputPath:o,cleanup:()=>this.safeUnlink(o)}}catch(t){if(t instanceof J)throw t;let n=t ins

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.0.0-alpha.111. 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: po-browse-tool: Host or code assembled from base64 fragments (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/po-browse-tool/0.0.0-alpha.111

## Findings with a location
- `dist/index.mjs:52` · Host or code assembled from base64 fragments — dist/index.mjs:52 · Host or code assembled from base64 fragments
- `dist/index.cjs:52` · Host or code assembled from base64 fragments — dist/index.cjs:52 · Host or code assembled from base64 fragments

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