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. 70 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 2 caught lines
Download .patchdiff --git a/refs_mcp/discovery.py b/refs_mcp/discovery.py --- a/refs_mcp/discovery.py +++ b/refs_mcp/discovery.py @@ -107,1 +107,0 @@ -contain ``%`` (URL-encoded credentials, e.g. ``https://user:pass%40@…``, diff --git a/tests/test_discovery.py b/tests/test_discovery.py --- a/tests/test_discovery.py +++ b/tests/test_discovery.py @@ -84,1 +84,0 @@ -"\turl = https://user:p%[email protected]/owner/bad-pct.git\n",
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.2. 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: refs-mcp: URL with embedded credentials (KillerSkills verdict caution 70)
## 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 70/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/refs-mcp/0.2.2 ## Findings with a location - `refs_mcp/discovery.py:107` · URL with embedded credentials — refs_mcp/discovery.py:107 · URL with embedded credentials — may be phishing or credential leaking - `tests/test_discovery.py:84` · URL with embedded credentials — tests/test_discovery.py:84 · URL with embedded credentials — may be phishing or credential leaking ## 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 foo/bar --clone && cd bar curl -s https://killerskills.ai/skills/pypi/refs-mcp/0.2.2/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.2.2 && git commit -am "refs-mcp: URL with embedded credentials" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/refs-mcp/0.2.2/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.