← sbuilder-mcp@0.112.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. 79 · Caution

Evidence

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

Diff · removes 2 caught lines

Download .patch
diff --git a/dist/transport/localfile.js b/dist/transport/localfile.js
--- a/dist/transport/localfile.js
+++ b/dist/transport/localfile.js
@@ -9,1 +9,0 @@
-* it exfiltrates (`~/.ssh/id_rsa` uploaded under `name:"x.png"` gets a public CDN
diff --git a/dist/transport/media.js b/dist/transport/media.js
--- a/dist/transport/media.js
+++ b/dist/transport/media.js
@@ -338,1 +338,0 @@
-// {path:"~/.ssh/id_rsa", name:"x.png"} uploads a key as an image to a public

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

## 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 79/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/npm/sbuilder-mcp/0.112.0

## Findings with a location
- `dist/transport/localfile.js:9` · References a credential file in the home directory — dist/transport/localfile.js:9 · References a credential file in the home directory
- `dist/transport/media.js:338` · References a credential file in the home directory — dist/transport/media.js:338 · References a credential file in the home directory

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