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. 64 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 2 caught lines
Download .patchdiff --git a/.claude/helpers/hook-handler.cjs b/.claude/helpers/hook-handler.cjs --- a/.claude/helpers/hook-handler.cjs +++ b/.claude/helpers/hook-handler.cjs @@ -219,1 +219,0 @@ -// 2. `prefix=` in the user npmrc ($npm_config_userconfig, else ~/.npmrc), diff --git a/README.zh-CN.md b/README.zh-CN.md --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -318,1 +318,0 @@ -<summary><strong>联邦能力</strong></summary> | | 能力 | 工作原理 | |---|---|---| | 🔒 | **零信任联邦** | 远程智能体初始均不受信任。身份通过 mTLS + ed25519 质询-应答机制证明。无需 API Key,无需共享密钥。 | | 🛡️
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 3.77.2. 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: claude-flow: References a credential file in the home directory (KillerSkills verdict caution 64)
## 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 64/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/claude-flow/3.77.2 ## Findings with a location - `.claude/helpers/hook-handler.cjs:219` · References a credential file in the home directory — .claude/helpers/hook-handler.cjs:219 · References a credential file in the home directory - `README.zh-CN.md:318` · Collapsed <details> block carrying instructions — README.zh-CN.md:318 · Collapsed <details> block carrying instructions ## 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 ruvnet/ruflo --clone && cd ruflo curl -s https://killerskills.ai/skills/npm/claude-flow/3.77.2/patch.diff | git apply --unidiff-zero git checkout -b killerskills/3.77.2 && git commit -am "claude-flow: References a credential file in the home directory" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/claude-flow/3.77.2/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.