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. 41 · Blocked
Evidence
- Contacted www.google.com: not declared and not needed for the documented job.
Diff · removes 1 caught line
Download .patchdiff --git a/SKILL.md b/SKILL.md --- a/SKILL.md +++ b/SKILL.md @@ -50,1 +50,0 @@ -<summary>手动安装(可选)</summary> 如果不想使用自动脚本,可以手动安装: ```bash # 安装 uv (Windows) irm https://astral.sh/uv/install.ps1 | iex # 安装 uv (macOS/Linux) curl -LsSf https://ast
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: weekly-report-openclaw: Contacted www.google.com: not declared and not needed for the documented job (KillerSkills verdict blocked 41)
## 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 **BLOCKED 41/100**. Summary: sends data to www.google.com. - Contacted www.google.com: not declared and not needed for the documented job. Full trace and findings: https://killerskills.ai/skills/clawhub/weekly-report-openclaw/1.0.0 ## Findings with a location - `SKILL.md:50` · Collapsed <details> block carrying instructions — SKILL.md:50 · Collapsed <details> block carrying instructions ## Proposed change The attached patch removes the 1 line 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.