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. 63 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/dist/clients.js b/dist/clients.js --- a/dist/clients.js +++ b/dist/clients.js @@ -581,1 +581,0 @@ -const body = text.replace(/^/, ''); diff --git a/src/clients.ts b/src/clients.ts --- a/src/clients.ts +++ b/src/clients.ts @@ -722,1 +722,0 @@ -const body = text.replace(/^/, ''); diff --git a/src/runner/workspace.ts b/src/runner/workspace.ts --- a/src/runner/workspace.ts +++ b/src/runner/workspace.ts @@ -218,1 +218,0 @@ -const parsed = JSON.parse(text.replace(/^/, '')); diff --git a/src/runner/config.ts b/src/runner/config.ts --- a/src/runner/config.ts +++ b/src/runner/config.ts @@ -111,1 +111,0 @@ -raw = JSON.parse(text.replace(/^/, ''));
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: bruce-comm: Hidden zero-width characters detected (KillerSkills verdict caution 63)
## 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 63/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/bruce-comm/1.0.0 ## Findings with a location - `dist/clients.js:581` · Hidden zero-width characters detected — dist/clients.js:581 · Hidden zero-width characters detected — may conceal content - `src/clients.ts:722` · Hidden zero-width characters detected — src/clients.ts:722 · Hidden zero-width characters detected — may conceal content - `src/runner/workspace.ts:218` · Hidden zero-width characters detected — src/runner/workspace.ts:218 · Hidden zero-width characters detected — may conceal content - `src/runner/config.ts:111` · Hidden zero-width characters detected — src/runner/config.ts:111 · 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._
# or from a terminal, under your own account: gh repo fork arijitaich-og1o/bruce-comm --clone && cd bruce-comm curl -s https://killerskills.ai/skills/glama/bruce-comm/1.0.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.0 && git commit -am "bruce-comm: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/bruce-comm/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.