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 16 caught lines
Download .patchdiff --git a/commands/items.py b/commands/items.py --- a/commands/items.py +++ b/commands/items.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/products.py b/commands/products.py --- a/commands/products.py +++ b/commands/products.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/cdash.py b/commands/cdash.py --- a/commands/cdash.py +++ b/commands/cdash.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/qrs.py b/commands/qrs.py --- a/commands/qrs.py +++ b/commands/qrs.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/ct_packages.py b/commands/ct_packages.py --- a/commands/ct_packages.py +++ b/commands/ct_packages.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/docs.py b/commands/docs.py --- a/commands/docs.py +++ b/commands/docs.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/batch.py b/commands/batch.py --- a/commands/batch.py +++ b/commands/batch.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/export.py b/commands/export.py --- a/commands/export.py +++ b/commands/export.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/search.py b/commands/search.py --- a/commands/search.py +++ b/commands/search.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/cache.py b/commands/cache.py --- a/commands/cache.py +++ b/commands/cache.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/rules.py b/commands/rules.py --- a/commands/rules.py +++ b/commands/rules.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/compare.py b/commands/compare.py --- a/commands/compare.py +++ b/commands/compare.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/adam.py b/commands/adam.py --- a/commands/adam.py +++ b/commands/adam.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/sdtm.py b/commands/sdtm.py --- a/commands/sdtm.py +++ b/commands/sdtm.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/ct.py b/commands/ct.py --- a/commands/ct.py +++ b/commands/ct.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3 diff --git a/commands/root.py b/commands/root.py --- a/commands/root.py +++ b/commands/root.py @@ -1,1 +1,0 @@ -#!/usr/bin/env python3
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: cdisc-library-api: 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.9.2) and scored it **CAUTION 66/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/cdisc-library-api/1.0.0 ## Findings with a location - `commands/items.py:1` · Hidden zero-width characters detected — commands/items.py:1 · Hidden zero-width characters detected — may conceal content - `commands/products.py:1` · Hidden zero-width characters detected — commands/products.py:1 · Hidden zero-width characters detected — may conceal content - `commands/cdash.py:1` · Hidden zero-width characters detected — commands/cdash.py:1 · Hidden zero-width characters detected — may conceal content - `commands/qrs.py:1` · Hidden zero-width characters detected — commands/qrs.py:1 · Hidden zero-width characters detected — may conceal content - `commands/ct_packages.py:1` · Hidden zero-width characters detected — commands/ct_packages.py:1 · Hidden zero-width characters detected — may conceal content - `commands/docs.py:1` · Hidden zero-width characters detected — commands/docs.py:1 · Hidden zero-width characters detected — may conceal content - `commands/batch.py:1` · Hidden zero-width characters detected — commands/batch.py:1 · Hidden zero-width characters detected — may conceal content - `commands/export.py:1` · Hidden zero-width characters detected — commands/export.py:1 · Hidden zero-width characters detected — may conceal content - `commands/search.py:1` · Hidden zero-width characters detected — commands/search.py:1 · Hidden zero-width characters detected — may conceal content - `commands/cache.py:1` · Hidden zero-width characters detected — commands/cache.py:1 · Hidden zero-width characters detected — may conceal content - `commands/rules.py:1` · Hidden zero-width characters detected — commands/rules.py:1 · Hidden zero-width characters detected — may conceal content - `commands/compare.py:1` · Hidden zero-width characters detected — commands/compare.py:1 · Hidden zero-width characters detected — may conceal content ## Proposed change The attached patch removes the 16 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._
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.