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/scripts/preserve-check.mjs b/scripts/preserve-check.mjs --- a/scripts/preserve-check.mjs +++ b/scripts/preserve-check.mjs @@ -60,1 +60,0 @@ -// ponytail: two-pass token extraction with delimiter stripping; digit grouping diff --git a/benchmark/eval-baseline.json b/benchmark/eval-baseline.json --- a/benchmark/eval-baseline.json +++ b/benchmark/eval-baseline.json @@ -1090,1 +1090,0 @@ -… maka penjajahan di atas dunia harus dihapuskan, karena tidak sesuai dengan perikemanusiaan dan perikeadilan.\n\nDan perjuangan pergerakan kemerdekaan Indonesi… @@ -1160,1 +1159,0 @@ -…", "text": "Candi Prambanan atau Candi Roro Jonggrang (bahasa Jawa: ꦕꦤ꧀ꦝꦶꦥꦿꦩ꧀ꦧꦤꦤ꧀, translit. Candhi Prambanan) adalah kompleks candi Hindu terbesar di In… diff --git a/README.md b/README.md --- a/README.md +++ b/README.md @@ -282,1 +282,0 @@ -humanizer-ignore
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.6.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: humanizer-lint: Credential pass-through configuration (KillerSkills verdict caution 63)
## 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 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/npm/humanizer-lint/1.6.0 ## Findings with a location - `scripts/preserve-check.mjs:60` · Credential pass-through configuration — scripts/preserve-check.mjs:60 · Credential pass-through configuration — agent relays sensitive credentials - `benchmark/eval-baseline.json:1160` · Hidden zero-width characters detected — benchmark/eval-baseline.json:1160 · Hidden zero-width characters detected — may conceal content - `benchmark/eval-baseline.json:1090` · Hidden zero-width characters detected — benchmark/eval-baseline.json:1090 · Hidden zero-width characters detected — may conceal content - `README.md:282` · HTML comment carrying imperative instructions to the agent — README.md:282 · HTML comment carrying imperative instructions to the agent ## 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 yanstd888/humanizer-lint --clone && cd humanizer-lint curl -s https://killerskills.ai/skills/npm/humanizer-lint/1.6.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.6.0 && git commit -am "humanizer-lint: Credential pass-through configuration" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/humanizer-lint/1.6.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.