Propose a patch

Evidence

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

diff --git a/credits.json b/credits.json
--- a/credits.json
+++ b/credits.json
@@ -600,1 +600,0 @@
-…[email protected][email protected]/node_modules/express-rate-limit", "licenseText": " # MIT License\n\nCopyright 2023 Nathan Friedly, Vedant K\n\nPermission is hereby…

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

## 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 70/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/axe-mcp-server/1.8.0

## Findings with a location
- `extension/vendor.bundle.js:2` · Base64 encoding combined with network call — extension/vendor.bundle.js:2 · Base64 encoding combined with network call — potential data exfiltration
- `credits.json:600` · Hidden zero-width characters detected — credits.json:600 · 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._