Propose a patch
A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 65 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 6 caught lines
Download .patchdiff --git a/packages/core/src/injection.ts b/packages/core/src/injection.ts
--- a/packages/core/src/injection.ts
+++ b/packages/core/src/injection.ts
@@ -26,1 +26,0 @@
-{ id: 'hidden-text', label: 'Hidden zero-width / invisible characters', re: /[--]/, weight: 0.6, kind: 'hidden-text' },
@@ -68,1 +67,0 @@
-excerpt: truncate(excerpt.replace(/[-]/g, '').replace(/\s+/g, ' '), 320),
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -212,1 +212,0 @@
-<summary><b>Full gateway API</b></summary> | Method | Route | Purpose | |---|---|---| | `GET` | `/api/state` | Snapshot: masked vault, policies, recipients, too
diff --git a/scripts/video/graphics.ts b/scripts/video/graphics.ts
--- a/scripts/video/graphics.ts
+++ b/scripts/video/graphics.ts
@@ -11,1 +11,0 @@
-const FONT = '<link href="https://fonts.googleapis.com/css2?family=Work+Sans:wght@400;500;600&display=block" rel="stylesheet">';
diff --git a/scripts/video/captions.ts b/scripts/video/captions.ts
--- a/scripts/video/captions.ts
+++ b/scripts/video/captions.ts
@@ -23,1 +23,0 @@
-`<!doctype html><html><head><link href="https://fonts.googleapis.com/css2?family=Work+Sans:wght@500;600&display=block" rel="stylesheet">
diff --git a/scripts/video/thumbnail.ts b/scripts/video/thumbnail.ts
--- a/scripts/video/thumbnail.ts
+++ b/scripts/video/thumbnail.ts
@@ -29,1 +29,0 @@
-`<!doctype html><html><head><link href="https://fonts.googleapis.com/css2?family=Work+Sans:wght@500;700;800&display=block" rel="stylesheet"><style>
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.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: consentry: Hidden zero-width characters detected (KillerSkills verdict caution 65)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) 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/glama/consentry/1.0.0 ## Findings with a location - `packages/core/src/injection.ts:26` · Hidden zero-width characters detected — packages/core/src/injection.ts:26 · Hidden zero-width characters detected — may conceal content - `packages/core/src/injection.ts:68` · Hidden zero-width characters detected — packages/core/src/injection.ts:68 · Hidden zero-width characters detected — may conceal content - `README.md:212` · Collapsed <details> block carrying instructions — README.md:212 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file - `scripts/video/graphics.ts:11` · URL with embedded credentials — scripts/video/graphics.ts:11 · URL with embedded credentials — may be phishing or credential leaking - `scripts/video/captions.ts:23` · URL with embedded credentials — scripts/video/captions.ts:23 · URL with embedded credentials — may be phishing or credential leaking - `scripts/video/thumbnail.ts:29` · URL with embedded credentials — scripts/video/thumbnail.ts:29 · URL with embedded credentials — may be phishing or credential leaking ## Proposed change The attached patch removes the 6 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._
# or from a terminal, under your own account: gh repo fork vnmoorthy/consentry --clone && cd consentry curl -s https://killerskills.ai/skills/glama/consentry/1.0.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.0 && git commit -am "consentry: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/consentry/1.0.0/patch.md)
We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.