← scopus-plus-mcp@0.24.0

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 .patch
diff --git a/src/scopus_mcp/importers.py b/src/scopus_mcp/importers.py
--- a/src/scopus_mcp/importers.py
+++ b/src/scopus_mcp/importers.py
@@ -46,1 +46,0 @@
-reader = csv.DictReader(io.StringIO(text.lstrip('')))
@@ -49,1 +48,0 @@
-row = {(k or '').strip().lstrip(''): v for k, v in row.items()}
@@ -127,1 +125,0 @@
-reader = csv.DictReader(io.StringIO(text.lstrip('')), delimiter='\t', quoting=csv.QUOTE_NONE)
@@ -130,1 +127,0 @@
-row = {(k or '').strip().lstrip(''): v for k, v in row.items()}
@@ -148,1 +144,0 @@
-head = text.lstrip('')[:4000]

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.24.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: scopus-plus-mcp: Hidden zero-width characters detected (KillerSkills verdict caution 75)

## 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 75/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/scopus-plus-mcp/0.24.0

## Findings with a location
- `src/scopus_mcp/importers.py:49` · Hidden zero-width characters detected — src/scopus_mcp/importers.py:49 · Hidden zero-width characters detected — may conceal content
- `src/scopus_mcp/importers.py:127` · Hidden zero-width characters detected — src/scopus_mcp/importers.py:127 · Hidden zero-width characters detected — may conceal content
- `src/scopus_mcp/importers.py:148` · Hidden zero-width characters detected — src/scopus_mcp/importers.py:148 · Hidden zero-width characters detected — may conceal content
- `src/scopus_mcp/importers.py:130` · Hidden zero-width characters detected — src/scopus_mcp/importers.py:130 · Hidden zero-width characters detected — may conceal content
- `src/scopus_mcp/importers.py:46` · Hidden zero-width characters detected — src/scopus_mcp/importers.py:46 · 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._
# or from a terminal, under your own account:
gh repo fork michalhron/scopus-plus-mcp --clone && cd scopus-plus-mcp
curl -s https://killerskills.ai/skills/pypi/scopus-plus-mcp/0.24.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.24.0 && git commit -am "scopus-plus-mcp: Hidden zero-width characters detected"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/scopus-plus-mcp/0.24.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.