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. 61 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 5 caught lines
Download .patchdiff --git a/scripts/deploy-contracts.ts b/scripts/deploy-contracts.ts
--- a/scripts/deploy-contracts.ts
+++ b/scripts/deploy-contracts.ts
@@ -1,1 +1,0 @@
-#!/usr/bin/env tsx
diff --git a/src/server/http.ts b/src/server/http.ts
--- a/src/server/http.ts
+++ b/src/server/http.ts
@@ -1,1 +1,0 @@
-/**
diff --git a/scripts/generate-env.ts b/scripts/generate-env.ts
--- a/scripts/generate-env.ts
+++ b/scripts/generate-env.ts
@@ -1,1 +1,0 @@
-#!/usr/bin/env tsx
diff --git a/src/wallet/coinbase.ts b/src/wallet/coinbase.ts
--- a/src/wallet/coinbase.ts
+++ b/src/wallet/coinbase.ts
@@ -1,1 +1,0 @@
-import { createPublicClient, http, type TransactionRequest, type Hash } from "viem";
diff --git a/src/security/replay.ts b/src/security/replay.ts
--- a/src/security/replay.ts
+++ b/src/security/replay.ts
@@ -1,1 +1,0 @@
-import { createHash } from "crypto";
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.4. 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: safelink: Hidden zero-width characters detected (KillerSkills verdict caution 61)
## 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 61/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/safelink/0.1.4 ## Findings with a location - `scripts/deploy-contracts.ts:1` · Hidden zero-width characters detected — scripts/deploy-contracts.ts:1 · Hidden zero-width characters detected — may conceal content - `src/server/http.ts:1` · Hidden zero-width characters detected — src/server/http.ts:1 · Hidden zero-width characters detected — may conceal content - `scripts/generate-env.ts:1` · Hidden zero-width characters detected — scripts/generate-env.ts:1 · Hidden zero-width characters detected — may conceal content - `src/wallet/coinbase.ts:1` · Hidden zero-width characters detected — src/wallet/coinbase.ts:1 · Hidden zero-width characters detected — may conceal content - `src/security/replay.ts:1` · Hidden zero-width characters detected — src/security/replay.ts:1 · Hidden zero-width characters detected — may conceal content ## Proposed change The attached patch removes the 5 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 charliebot8888/SafeLink --clone && cd SafeLink curl -s https://killerskills.ai/skills/clawhub/safelink/0.1.4/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.1.4 && git commit -am "safelink: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/safelink/0.1.4/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.