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. 72 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 5 caught lines
Download .patchdiff --git a/argocd_mcp_server/config.py b/argocd_mcp_server/config.py
--- a/argocd_mcp_server/config.py
+++ b/argocd_mcp_server/config.py
@@ -31,1 +31,0 @@
-SSH_PRIVATE_KEY_PATH: Path to SSH private key file (default: ~/.ssh/id_rsa).
@@ -35,1 +34,0 @@
-ssh_private_key_path: str = '~/.ssh/id_rsa'
@@ -117,1 +115,0 @@
-ssh_private_key_path=os.getenv('SSH_PRIVATE_KEY_PATH', '~/.ssh/id_rsa'),
diff --git a/skills/onboarding-argocd-repositories-and-projects/SKILL.md b/skills/onboarding-argocd-repositories-and-projects/SKILL.md
--- a/skills/onboarding-argocd-repositories-and-projects/SKILL.md
+++ b/skills/onboarding-argocd-repositories-and-projects/SKILL.md
@@ -26,1 +26,0 @@
-- **`ssh://...` or `git@...` URLs**: Reads the SSH private key from `SSH_PRIVATE_KEY_PATH` (default `~/.ssh/id_rsa`) on the MCP server host.
diff --git a/docker-compose.yml b/docker-compose.yml
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -44,1 +44,0 @@
-- ${HOME}/.ssh/id_rsa:/app/.ssh/id_rsa:ro
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.4.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: talkops-argocd-mcp-server: References a credential file in the home directory (KillerSkills verdict caution 72)
## 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 72/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/talkops-argocd-mcp-server/0.4.0 ## Findings with a location - `argocd_mcp_server/config.py:31` · References a credential file in the home directory — argocd_mcp_server/config.py:31 · References a credential file in the home directory - `skills/onboarding-argocd-repositories-and-projects/SKILL.md:26` · References a credential file in the home directory — skills/onboarding-argocd-repositories-and-projects/SKILL.md:26 · References a credential file in the home directory - `argocd_mcp_server/config.py:35` · References a credential file in the home directory — argocd_mcp_server/config.py:35 · References a credential file in the home directory - `argocd_mcp_server/config.py:117` · References a credential file in the home directory — argocd_mcp_server/config.py:117 · References a credential file in the home directory - `docker-compose.yml:44` · References a credential file in the home directory — docker-compose.yml:44 · References a credential file in the home directory ## Proposed change The attached patch removes the 5 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 talkops-ai/talkops-mcp --clone && cd talkops-mcp curl -s https://killerskills.ai/skills/pypi/talkops-argocd-mcp-server/0.4.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.4.0 && git commit -am "talkops-argocd-mcp-server: References a credential file in the home directory" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/talkops-argocd-mcp-server/0.4.0/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.