← keenetic-mcp@0.0.0-dev

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 .patch
diff --git a/src/cli/init.ts b/src/cli/init.ts
--- a/src/cli/init.ts
+++ b/src/cli/init.ts
@@ -90,1 +90,0 @@
-const keyPath = expandHome((await deps.prompt('Private key path', '~/.ssh/id_ed25519')) || '~/.ssh/id_ed25519');
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -1,1 +1,0 @@
-keenetic-mcp, the Keenetic MCP server: secure automation and control for Keenetic routers via the Model Context Protocol. Your AI client talks to the MCP server

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.0.0-dev. 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: keenetic-mcp: 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/glama/keenetic-mcp/0.0.0-dev

## Findings with a location
- `src/cli/init.ts:90` · References a credential file in the home directory — src/cli/init.ts:90 · References a credential file in the home directory
- `README.md:1` · Image alt text carrying instructions — README.md:1 · Image alt text 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 ML-senior/keenetic-mcp --clone && cd keenetic-mcp
curl -s https://killerskills.ai/skills/glama/keenetic-mcp/0.0.0-dev/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.0.0-dev && git commit -am "keenetic-mcp: References a credential file in the home directory"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/keenetic-mcp/0.0.0-dev/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.