← stackchan-mcp@0.20.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. 75 · Caution

Evidence

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

Diff · removes 4 caught lines

Download .patch
diff --git a/stackchan_mcp/cli.py b/stackchan_mcp/cli.py
--- a/stackchan_mcp/cli.py
+++ b/stackchan_mcp/cli.py
@@ -380,1 +380,0 @@
-- ``https://user:pass@host/path`` → ``https://***:***@host/path``
diff --git a/tests/test_emoji_expression.py b/tests/test_emoji_expression.py
--- a/tests/test_emoji_expression.py
+++ b/tests/test_emoji_expression.py
@@ -44,1 +44,0 @@
-assert strip_emoji_for_plain_tts("work 🧑‍💻 done") == "work done"
diff --git a/tests/test_cli.py b/tests/test_cli.py
--- a/tests/test_cli.py
+++ b/tests/test_cli.py
@@ -618,1 +618,0 @@
-out = _redact_url_secrets("https://user:[email protected]:8443/capture")
@@ -693,1 +692,0 @@
-"https://signer:[email protected]/capture?token=tk_abc123",

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.20.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: stackchan-mcp: URL with embedded credentials (KillerSkills verdict caution 75)

## 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 75/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/stackchan-mcp/0.20.0

## Findings with a location
- `stackchan_mcp/cli.py:380` · URL with embedded credentials — stackchan_mcp/cli.py:380 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_emoji_expression.py:44` · Hidden zero-width characters detected — tests/test_emoji_expression.py:44 · Hidden zero-width characters detected — may conceal content
- `tests/test_cli.py:618` · URL with embedded credentials — tests/test_cli.py:618 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_cli.py:693` · URL with embedded credentials — tests/test_cli.py:693 · URL with embedded credentials — may be phishing or credential leaking

## 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 kisaragi-mochi/stackchan-mcp --clone && cd stackchan-mcp
curl -s https://killerskills.ai/skills/pypi/stackchan-mcp/0.20.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.20.0 && git commit -am "stackchan-mcp: URL with embedded credentials"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/stackchan-mcp/0.20.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.