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. 60 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 10 caught lines
Download .patchdiff --git a/README.md b/README.md --- a/README.md +++ b/README.md @@ -227,1 +227,0 @@ -<summary><b>Jaeger</b></summary> ```bash BACKEND_TYPE=jaeger BACKEND_URL=http://localhost:16686 ``` No API key required. **`search_traces` and `search_spans_too @@ -239,1 +238,0 @@ -<summary><b>Grafana Tempo</b></summary> ```bash BACKEND_TYPE=tempo BACKEND_URL=http://localhost:3200 ``` No API key required for a local/self-hosted install. Se @@ -260,1 +258,0 @@ -<summary><b>Traceloop</b></summary> ```bash BACKEND_TYPE=traceloop BACKEND_URL=https://api.traceloop.com BACKEND_API_KEY=your_api_key_here ``` The API key encod @@ -273,1 +270,0 @@ -<summary><b>Datadog</b></summary> ```bash BACKEND_TYPE=datadog # US site (default): https://api.datadoghq.com # EU site: https://api.datadoghq.eu BACKEND_URL=ht diff --git a/src/opentelemetry_mcp/security.py b/src/opentelemetry_mcp/security.py --- a/src/opentelemetry_mcp/security.py +++ b/src/opentelemetry_mcp/security.py @@ -139,1 +139,0 @@ -# literal "@" inside the password (`https://u:p@[email protected]/` is host h.test, diff --git a/tests/test_config.py b/tests/test_config.py --- a/tests/test_config.py +++ b/tests/test_config.py @@ -178,1 +178,0 @@ -BackendConfig(type="jaeger", url=HttpUrl(f"https://u:{VFY_MARKER}@h.test")) @@ -194,1 +193,0 @@ -config.apply_cli_overrides(backend_url=f"https://u:{VFY_MARKER}@h.test") @@ -203,1 +201,0 @@ -monkeypatch.setenv("SECONDARY_BACKEND_URL", f"https://u:{VFY_MARKER}@h.test") @@ -218,1 +215,0 @@ -BackendConfig(type="jaeger", url=HttpUrl(f"http://u:{VFY_MARKER}@169.254.169.254/")) @@ -289,1 +285,0 @@ -monkeypatch.setenv("BACKEND_URL", f"https://{LONG_USER}:{LONG_PASSWORD}@{tail}")
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.13.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: tracehub-mcp: Collapsed <details> block carrying instructions (KillerSkills verdict caution 60)
## 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 60/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/tracehub-mcp/0.13.2 ## Findings with a location - `README.md:239` · Collapsed <details> block carrying instructions — README.md:239 · Collapsed <details> block carrying instructions - `README.md:260` · Collapsed <details> block carrying instructions — README.md:260 · Collapsed <details> block carrying instructions - `README.md:227` · Collapsed <details> block carrying instructions — README.md:227 · Collapsed <details> block carrying instructions - `README.md:273` · Collapsed <details> block carrying instructions — README.md:273 · Collapsed <details> block carrying instructions - `src/opentelemetry_mcp/security.py:139` · URL with embedded credentials — src/opentelemetry_mcp/security.py:139 · URL with embedded credentials — may be phishing or credential leaking - `tests/test_config.py:178` · URL with embedded credentials — tests/test_config.py:178 · URL with embedded credentials — may be phishing or credential leaking - `tests/test_config.py:203` · URL with embedded credentials — tests/test_config.py:203 · URL with embedded credentials — may be phishing or credential leaking - `tests/test_config.py:194` · URL with embedded credentials — tests/test_config.py:194 · URL with embedded credentials — may be phishing or credential leaking - `tests/test_config.py:289` · URL with embedded credentials — tests/test_config.py:289 · URL with embedded credentials — may be phishing or credential leaking - `tests/test_config.py:218` · URL with embedded credentials — tests/test_config.py:218 · URL with embedded credentials — may be phishing or credential leaking ## Proposed change The attached patch removes the 10 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 mcpsmiths/tracehub-mcp --clone && cd tracehub-mcp curl -s https://killerskills.ai/skills/pypi/tracehub-mcp/0.13.2/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.13.2 && git commit -am "tracehub-mcp: Collapsed <details> block carrying instructions" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/tracehub-mcp/0.13.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.