← scope-analytics-mcp@0.2.1

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

Evidence

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

Diff · removes 5 caught lines

Download .patch
diff --git a/scope_mcp/agent_tools.py b/scope_mcp/agent_tools.py
--- a/scope_mcp/agent_tools.py
+++ b/scope_mcp/agent_tools.py
@@ -298,1 +298,0 @@
-https://user:token@host/x?t=1 → https://host/x; [email protected]:org/repo → github.com:org/repo."""
diff --git a/tests/test_agent_tools.py b/tests/test_agent_tools.py
--- a/tests/test_agent_tools.py
+++ b/tests/test_agent_tools.py
@@ -236,1 +236,0 @@
-("remote", "get-url", "origin"): R(0, "https://wally:[email protected]/acme/app.git\n"),
@@ -682,1 +681,0 @@
-(tmp_path / ".env").write_text("SCOPE_API_KEY=sk_first\nSCOPE_API_KEY=sk_last\n", encoding="utf-8")
@@ -684,1 +682,0 @@
-(tmp_path / ".env").write_text("SCOPE_API_KEY=sk_only\n", encoding="utf-8")
diff --git a/scope_mcp/setup.py b/scope_mcp/setup.py
--- a/scope_mcp/setup.py
+++ b/scope_mcp/setup.py
@@ -98,1 +98,0 @@
-for line in (text or "").lstrip("").splitlines():

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

## 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 73/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/scope-analytics-mcp/0.2.1

## Findings with a location
- `scope_mcp/agent_tools.py:298` · URL with embedded credentials — scope_mcp/agent_tools.py:298 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_agent_tools.py:682` · Hidden zero-width characters detected — tests/test_agent_tools.py:682 · Hidden zero-width characters detected — may conceal content
- `scope_mcp/setup.py:98` · Hidden zero-width characters detected — scope_mcp/setup.py:98 · Hidden zero-width characters detected — may conceal content
- `tests/test_agent_tools.py:236` · URL with embedded credentials — tests/test_agent_tools.py:236 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_agent_tools.py:684` · Hidden zero-width characters detected — tests/test_agent_tools.py:684 · Hidden zero-width characters detected — may conceal content

## 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._
No GitHub source is recorded for this package, so there is nothing to open; paste the body into the registry's support channel.

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.