← promcp@0.5.2
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. 64 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 12 caught lines
Download .patchdiff --git a/promcp/adapters/__init__.py b/promcp/adapters/__init__.py --- a/promcp/adapters/__init__.py +++ b/promcp/adapters/__init__.py @@ -1,1 +1,0 @@ -# proMCP Adapters — raw, anthropic diff --git a/promcp/adapters/raw.py b/promcp/adapters/raw.py --- a/promcp/adapters/raw.py +++ b/promcp/adapters/raw.py @@ -1,1 +1,0 @@ -""" diff --git a/promcp/decorators.py b/promcp/decorators.py --- a/promcp/decorators.py +++ b/promcp/decorators.py @@ -1,1 +1,0 @@ -""" diff --git a/promcp/exceptions.py b/promcp/exceptions.py --- a/promcp/exceptions.py +++ b/promcp/exceptions.py @@ -1,1 +1,0 @@ -""" diff --git a/promcp/contracts.py b/promcp/contracts.py --- a/promcp/contracts.py +++ b/promcp/contracts.py @@ -1,1 +1,0 @@ -""" diff --git a/promcp/__init__.py b/promcp/__init__.py --- a/promcp/__init__.py +++ b/promcp/__init__.py @@ -1,1 +1,0 @@ -""" diff --git a/promcp/adapters/anthropic.py b/promcp/adapters/anthropic.py --- a/promcp/adapters/anthropic.py +++ b/promcp/adapters/anthropic.py @@ -1,1 +1,0 @@ -""" diff --git a/promcp/linter/__init__.py b/promcp/linter/__init__.py --- a/promcp/linter/__init__.py +++ b/promcp/linter/__init__.py @@ -1,1 +1,0 @@ -from promcp.linter.checker import ( # noqa: F401 diff --git a/promcp/registry.py b/promcp/registry.py --- a/promcp/registry.py +++ b/promcp/registry.py @@ -1,1 +1,0 @@ -""" diff --git a/promcp/linter/checker.py b/promcp/linter/checker.py --- a/promcp/linter/checker.py +++ b/promcp/linter/checker.py @@ -1,1 +1,0 @@ -""" diff --git a/promcp/linter/cli.py b/promcp/linter/cli.py --- a/promcp/linter/cli.py +++ b/promcp/linter/cli.py @@ -1,1 +1,0 @@ -""" diff --git a/tests/test_decorators.py b/tests/test_decorators.py --- a/tests/test_decorators.py +++ b/tests/test_decorators.py @@ -1,1 +1,0 @@ -"""
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.5.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: promcp: Hidden zero-width characters detected (KillerSkills verdict caution 64)
## 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 64/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/pypi/promcp/0.5.2 ## Findings with a location - `promcp/adapters/__init__.py:1` · Hidden zero-width characters detected — promcp/adapters/__init__.py:1 · Hidden zero-width characters detected — may conceal content - `promcp/adapters/raw.py:1` · Hidden zero-width characters detected — promcp/adapters/raw.py:1 · Hidden zero-width characters detected — may conceal content - `promcp/decorators.py:1` · Hidden zero-width characters detected — promcp/decorators.py:1 · Hidden zero-width characters detected — may conceal content - `promcp/exceptions.py:1` · Hidden zero-width characters detected — promcp/exceptions.py:1 · Hidden zero-width characters detected — may conceal content - `promcp/contracts.py:1` · Hidden zero-width characters detected — promcp/contracts.py:1 · Hidden zero-width characters detected — may conceal content - `promcp/__init__.py:1` · Hidden zero-width characters detected — promcp/__init__.py:1 · Hidden zero-width characters detected — may conceal content - `promcp/adapters/anthropic.py:1` · Hidden zero-width characters detected — promcp/adapters/anthropic.py:1 · Hidden zero-width characters detected — may conceal content - `promcp/linter/__init__.py:1` · Hidden zero-width characters detected — promcp/linter/__init__.py:1 · Hidden zero-width characters detected — may conceal content - `promcp/registry.py:1` · Hidden zero-width characters detected — promcp/registry.py:1 · Hidden zero-width characters detected — may conceal content - `promcp/linter/checker.py:1` · Hidden zero-width characters detected — promcp/linter/checker.py:1 · Hidden zero-width characters detected — may conceal content - `promcp/linter/cli.py:1` · Hidden zero-width characters detected — promcp/linter/cli.py:1 · Hidden zero-width characters detected — may conceal content - `tests/test_decorators.py:1` · Hidden zero-width characters detected — tests/test_decorators.py:1 · Hidden zero-width characters detected — may conceal content ## Proposed change The attached patch removes the 12 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 alexlqi/promcp --clone && cd promcp curl -s https://killerskills.ai/skills/pypi/promcp/0.5.2/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.5.2 && git commit -am "promcp: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/promcp/0.5.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.