← kordoc@4.24.49

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. 66 · Caution

Evidence

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

Diff · removes 2 caught lines

Download .patch
diff --git a/dist/chunk-PMGJQWSW.js b/dist/chunk-PMGJQWSW.js
--- a/dist/chunk-PMGJQWSW.js
+++ b/dist/chunk-PMGJQWSW.js
@@ -76,1 +76,0 @@
-raw = JSON.parse(text.replace(/^/, ""));
diff --git a/dist/cli.js b/dist/cli.js
--- a/dist/cli.js
+++ b/dist/cli.js
@@ -534,1 +534,0 @@
-const jsonContent = readFileSync2(jsonPath, "utf-8").replace(/^/, "");

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

## 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 66/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/kordoc/4.24.49

## Findings with a location
- `dist/chunk-PMGJQWSW.js:76` · Hidden zero-width characters detected — dist/chunk-PMGJQWSW.js:76 · Hidden zero-width characters detected — may conceal content
- `dist/cli.js:534` · Hidden zero-width characters detected — dist/cli.js:534 · Hidden zero-width characters detected — may conceal content

## Proposed change
The attached patch removes the 2 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 chrisryugj/kordoc --clone && cd kordoc
curl -s https://killerskills.ai/skills/npm/kordoc/4.24.49/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/4.24.49 && git commit -am "kordoc: Hidden zero-width characters detected"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/kordoc/4.24.49/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.