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. 60 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 2 caught lines
Download .patchdiff --git a/output/parsed_2023211588-黄杰-肖勇波.json b/output/parsed_2023211588-黄杰-肖勇波.json --- a/output/parsed_2023211588-黄杰-肖勇波.json +++ b/output/parsed_2023211588-黄杰-肖勇波.json @@ -989,1 +989,0 @@ -"content": "需求预测:基于历史消耗数据,采用指数平滑法或移动平均法预测未来单位时间(如月)的平均需求量 dˉ 及需求标准差 σd。" @@ -993,1 +992,0 @@ -"content": "采购提前期:从下单到入库的时间长度 LL(单位与需求周期一致),并考虑提前期的波动标准差 σL(若数据支持)。"
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.5.6. 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: thu-thesis: Hidden zero-width characters detected (KillerSkills verdict caution 60)
## 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 60/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/thu-thesis/1.5.6 ## Findings with a location - `output/parsed_2023211588-黄杰-肖勇波.json:993` · Hidden zero-width characters detected — output/parsed_2023211588-黄杰-肖勇波.json:993 · Hidden zero-width characters detected — may conceal content - `output/parsed_2023211588-黄杰-肖勇波.json:989` · Hidden zero-width characters detected — output/parsed_2023211588-黄杰-肖勇波.json:989 · 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 tuna/thuthesis --clone && cd thuthesis curl -s https://killerskills.ai/skills/clawhub/thu-thesis/1.5.6/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.5.6 && git commit -am "thu-thesis: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/thu-thesis/1.5.6/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.