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 5 caught lines
Download .patchdiff --git a/tests/test_skill_bundle.py b/tests/test_skill_bundle.py --- a/tests/test_skill_bundle.py +++ b/tests/test_skill_bundle.py @@ -119,1 +119,0 @@ -base_url="https://name:[email protected]/v1?token=topsecret", @@ -120,1 +119,0 @@ -qdrant_url="https://name:[email protected]?token=topsecret", diff --git a/tests/test_first_run.py b/tests/test_first_run.py --- a/tests/test_first_run.py +++ b/tests/test_first_run.py @@ -148,1 +148,0 @@ -config.write_text(json.dumps({"qdrant_url": "http://alice:password@localhost:6333/?token=private"})) @@ -152,1 +151,0 @@ -raise RuntimeError("request http://alice:password@localhost:6333/?token=private failed") diff --git a/src/roo_code_index_bridge_mcp/setup.py b/src/roo_code_index_bridge_mcp/setup.py --- a/src/roo_code_index_bridge_mcp/setup.py +++ b/src/roo_code_index_bridge_mcp/setup.py @@ -1875,1 +1875,0 @@ -targets.append(registry.home / ".codex" / "AGENTS.md")
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.6.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: roo-code-index-bridge-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.8.1) and scored it **CAUTION 75/100**. Summary: calls astral.sh only, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/pypi/roo-code-index-bridge-mcp/0.6.0 ## Findings with a location - `tests/test_skill_bundle.py:119` · URL with embedded credentials — tests/test_skill_bundle.py:119 · URL with embedded credentials — may be phishing or credential leaking - `tests/test_skill_bundle.py:120` · URL with embedded credentials — tests/test_skill_bundle.py:120 · URL with embedded credentials — may be phishing or credential leaking - `tests/test_first_run.py:148` · URL with embedded credentials — tests/test_first_run.py:148 · URL with embedded credentials — may be phishing or credential leaking - `src/roo_code_index_bridge_mcp/setup.py:1875` · Instructs the agent to modify its persistent memory or instruction files — src/roo_code_index_bridge_mcp/setup.py:1875 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `tests/test_first_run.py:152` · URL with embedded credentials — tests/test_first_run.py:152 · URL with embedded credentials — may be phishing or credential leaking ## Proposed change The attached patch removes the 5 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 prakashgarg91/roo-code-index-bridge-mcp --clone && cd roo-code-index-bridge-mcp curl -s https://killerskills.ai/skills/pypi/roo-code-index-bridge-mcp/0.6.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.6.0 && git commit -am "roo-code-index-bridge-mcp: URL with embedded credentials" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/roo-code-index-bridge-mcp/0.6.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.