← github-passwordless-setup@1.0.0

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

  • Read ~/.ssh/id_ed25519.pub in the decoy home directory.

Diff · removes 12 caught lines

Download .patch
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -68,1 +68,0 @@
-- Press Enter for default location (`~/.ssh/id_ed25519`)
@@ -76,1 +75,0 @@
-cat ~/.ssh/id_ed25519.pub | pbcopy
@@ -79,1 +77,0 @@
-cat ~/.ssh/id_ed25519.pub | xclip -selection clipboard
@@ -82,1 +79,0 @@
-cat ~/.ssh/id_ed25519.pub | xsel --clipboard
@@ -85,1 +81,0 @@
-cat ~/.ssh/id_ed25519.pub
@@ -153,1 +148,0 @@
-# Then paste your token and press Enter
diff --git a/setup.sh b/setup.sh
--- a/setup.sh
+++ b/setup.sh
@@ -35,1 +35,0 @@
-if [ -f ~/.ssh/id_ed25519.pub ]; then
@@ -37,1 +36,0 @@
-SSH_KEY_PATH=~/.ssh/id_ed25519.pub
@@ -38,1 +36,0 @@
-elif [ -f ~/.ssh/id_rsa.pub ]; then
@@ -40,1 +37,0 @@
-SSH_KEY_PATH=~/.ssh/id_rsa.pub
@@ -48,1 +44,0 @@
-ssh-keygen -t ed25519 -C "$USER_EMAIL" -f ~/.ssh/id_ed25519 -N ""
diff --git a/verify.sh b/verify.sh
--- a/verify.sh
+++ b/verify.sh
@@ -18,1 +18,0 @@
-if [ -f ~/.ssh/id_ed25519.pub ] || [ -f ~/.ssh/id_rsa.pub ]; then

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: github-passwordless-setup: Read ~/.ssh/id_ed25519.pub in the decoy home directory (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: reads credential files.

- Read ~/.ssh/id_ed25519.pub in the decoy home directory.

Full trace and findings: https://killerskills.ai/skills/clawhub/github-passwordless-setup/1.0.0

## Findings with a location
- `SKILL.md:82` · References a credential file in the home directory — SKILL.md:82 · References a credential file in the home directory
- `SKILL.md:85` · Reads credential paths from the home directory — SKILL.md:85 · Reads credential paths from the home directory
- `SKILL.md:68` · References a credential file in the home directory — SKILL.md:68 · References a credential file in the home directory
- `SKILL.md:79` · Reads credential paths from the home directory — SKILL.md:79 · Reads credential paths from the home directory
- `SKILL.md:76` · Reads credential paths from the home directory — SKILL.md:76 · Reads credential paths from the home directory
- `SKILL.md:76` · References a credential file in the home directory — SKILL.md:76 · References a credential file in the home directory
- `SKILL.md:82` · Reads credential paths from the home directory — SKILL.md:82 · Reads credential paths from the home directory
- `SKILL.md:68` · Reads credential paths from the home directory — SKILL.md:68 · Reads credential paths from the home directory
- `SKILL.md:79` · References a credential file in the home directory — SKILL.md:79 · References a credential file in the home directory
- `setup.sh:35` · References a credential file in the home directory — setup.sh:35 · References a credential file in the home directory
- `setup.sh:40` · References a credential file in the home directory — setup.sh:40 · References a credential file in the home directory
- `SKILL.md:85` · References a credential file in the home directory — SKILL.md:85 · References a credential file in the home directory

## Proposed change
The attached patch removes the 12 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 settings/ssh --clone && cd ssh
curl -s https://killerskills.ai/skills/clawhub/github-passwordless-setup/1.0.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.0.0 && git commit -am "github-passwordless-setup: Read ~/.ssh/id_ed25519.pub in the decoy home directory"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/github-passwordless-setup/1.0.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.