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. 73 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/.agents/skills/gh-cli/SKILL.md b/.agents/skills/gh-cli/SKILL.md --- a/.agents/skills/gh-cli/SKILL.md +++ b/.agents/skills/gh-cli/SKILL.md @@ -656,1 +656,0 @@ -gh repo deploy-key add ~/.ssh/id_rsa.pub \ @@ -1730,1 +1729,0 @@ -gh ssh-key add ~/.ssh/id_rsa.pub --title "My laptop" @@ -1733,1 +1731,0 @@ -gh ssh-key add ~/.ssh/id_ed25519.pub --type "authentication" @@ -1749,1 +1746,0 @@ -gh gpg-key add ~/.ssh/id_rsa.pub
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.1. 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: mcp-bitbucket-dc: References a credential file in the home directory (KillerSkills verdict caution 73)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8) and scored it **CAUTION 73/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/pypi/mcp-bitbucket-dc/1.0.1 ## Findings with a location - `.agents/skills/gh-cli/SKILL.md:656` · References a credential file in the home directory — .agents/skills/gh-cli/SKILL.md:656 · References a credential file in the home directory - `.agents/skills/gh-cli/SKILL.md:1749` · References a credential file in the home directory — .agents/skills/gh-cli/SKILL.md:1749 · References a credential file in the home directory - `.agents/skills/gh-cli/SKILL.md:1730` · References a credential file in the home directory — .agents/skills/gh-cli/SKILL.md:1730 · References a credential file in the home directory - `.agents/skills/gh-cli/SKILL.md:1733` · References a credential file in the home directory — .agents/skills/gh-cli/SKILL.md:1733 · References a credential file in the home directory ## 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 christopherekfeldt/mcp-bitbucket-dc --clone && cd mcp-bitbucket-dc curl -s https://killerskills.ai/skills/pypi/mcp-bitbucket-dc/1.0.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.1 && git commit -am "mcp-bitbucket-dc: References a credential file in the home directory" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/mcp-bitbucket-dc/1.0.1/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.