Propose a patch

Evidence

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

diff --git a/lib/fix/apply.js b/lib/fix/apply.js
--- a/lib/fix/apply.js
+++ b/lib/fix/apply.js
@@ -41,1 +41,0 @@
-// Code points HFS+ ignores in names, so ".g‌it" is ".git" on macOS (CVE-2014-9390).
@@ -42,1 +41,0 @@
-const IGNORABLE = /[​-‏‪-‮⁠-⁤-]/g;
diff --git a/src/card/model.js b/src/card/model.js
--- a/src/card/model.js
+++ b/src/card/model.js
@@ -38,1 +38,0 @@
-* (`pkg@https://user:pw@host/pkg.tgz?token=x`, `file:/Users/me/x.tgz`), so:
diff --git a/lib/retirejs.js b/lib/retirejs.js
--- a/lib/retirejs.js
+++ b/lib/retirejs.js
@@ -9,1 +9,0 @@
-*   2. File content pattern matching (/*! jQuery v3.5.1 *​/)

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

## 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 68/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/penthera/2.4.0

## Findings with a location
- `lib/fix/apply.js:42` · Hidden zero-width characters detected — lib/fix/apply.js:42 · Hidden zero-width characters detected — may conceal content
- `src/card/model.js:38` · URL with embedded credentials — src/card/model.js:38 · URL with embedded credentials — may be phishing or credential leaking
- `lib/fix/apply.js:41` · Hidden zero-width characters detected — lib/fix/apply.js:41 · Hidden zero-width characters detected — may conceal content
- `lib/retirejs.js:9` · Hidden zero-width characters detected — lib/retirejs.js:9 · 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._