← terminal-mcp@0.1.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. 65 · Caution

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 4 caught lines

Download .patch
diff --git a/scripts/smoke.ts b/scripts/smoke.ts
--- a/scripts/smoke.ts
+++ b/scripts/smoke.ts
@@ -103,1 +103,0 @@
-const ssh = await call("run_command", { command: "cat ~/.ssh/id_ed25519 ~/.ssh/id_rsa 2>&1 | head -2" });
@@ -105,1 +104,0 @@
-"kernel sandbox blocks reading ~/.ssh",
@@ -110,1 +108,0 @@
-console.log("  SKIP  ~/.ssh read denial (no ~/.ssh on this machine)");
diff --git a/worker/src/index.ts b/worker/src/index.ts
--- a/worker/src/index.ts
+++ b/worker/src/index.ts
@@ -32,1 +32,0 @@
-"Unauthorized. Provide the relay token as ?token=…, an Authorization: Bearer header, " +

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.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: terminal-mcp: References a credential file in the home directory (KillerSkills verdict caution 65)

## 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 65/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/terminal-mcp/0.1.0

## Findings with a location
- `scripts/smoke.ts:103` · References a credential file in the home directory — scripts/smoke.ts:103 · References a credential file in the home directory
- `scripts/smoke.ts:105` · Reads credential paths from the home directory — scripts/smoke.ts:105 · Reads credential paths from the home directory
- `scripts/smoke.ts:103` · Reads credential paths from the home directory — scripts/smoke.ts:103 · Reads credential paths from the home directory
- `scripts/smoke.ts:110` · Reads credential paths from the home directory — scripts/smoke.ts:110 · Reads credential paths from the home directory
- `worker/src/index.ts:32` · Credential pass-through configuration — worker/src/index.ts:32 · Credential pass-through configuration — agent relays sensitive credentials

## 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 Parithosh-Varma/terminal-mcp --clone && cd terminal-mcp
curl -s https://killerskills.ai/skills/glama/terminal-mcp/0.1.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.1.0 && git commit -am "terminal-mcp: References a credential file in the home directory"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/terminal-mcp/0.1.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.