← ris-mcp@0.2.3

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. 57 · Caution

Evidence

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

Diff · removes 1 caught line

Download .patch
diff --git a/docs/index.html b/docs/index.html
--- a/docs/index.html
+++ b/docs/index.html
@@ -443,1 +443,0 @@
-<summary class="cursor-pointer px-5 py-4 font-medium"> <span data-lang="en">Advanced: start with one court source</span> <span data-lang="de">Fortgeschritten: z

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

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 57/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/ris-mcp/0.2.3

## Findings with a location
- `tests/fixtures/bvwg_search_page1.json:1` · URL with embedded credentials — tests/fixtures/bvwg_search_page1.json:1 · URL with embedded credentials — may be phishing or credential leaking
- `docs/index.html:443` · Collapsed <details> block carrying instructions — docs/index.html:443 · Collapsed <details> block carrying instructions · informational: not an instruction file

## Proposed change
The attached patch removes the 1 line 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 jonashertner/ris-mcp --clone && cd ris-mcp
curl -s https://killerskills.ai/skills/pypi/ris-mcp/0.2.3/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.2.3 && git commit -am "ris-mcp: URL with embedded credentials"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/ris-mcp/0.2.3/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.