← data-query@1.0.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. 70 · Caution

Evidence

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

Diff · removes 8 caught lines

Download .patch
diff --git a/venv_dm/lib/python3.14/site-packages/pip/_internal/utils/unpacking.py b/venv_dm/lib/python3.14/site-packages/pip/_internal/utils/unpacking.py
--- a/venv_dm/lib/python3.14/site-packages/pip/_internal/utils/unpacking.py
+++ b/venv_dm/lib/python3.14/site-packages/pip/_internal/utils/unpacking.py
@@ -272,1 +272,0 @@
-# NOTE: This function can be removed once pip requires CPython ≥ 3.12.​
diff --git a/venv_dm/lib/python3.14/site-packages/pip/_vendor/pkg_resources/__init__.py b/venv_dm/lib/python3.14/site-packages/pip/_vendor/pkg_resources/__init__.py
--- a/venv_dm/lib/python3.14/site-packages/pip/_vendor/pkg_resources/__init__.py
+++ b/venv_dm/lib/python3.14/site-packages/pip/_vendor/pkg_resources/__init__.py
@@ -1714,1 +1714,0 @@
-exec(code, namespace, namespace)
@@ -1725,1 +1724,0 @@
-exec(script_code, namespace, namespace)
diff --git a/venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/util/url.py b/venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/util/url.py
--- a/venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/util/url.py
+++ b/venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/util/url.py
@@ -148,1 +148,0 @@
-'http://username:[email protected]:80/path?query#fragment'
diff --git a/venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/formatters/__init__.py b/venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/formatters/__init__.py
--- a/venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/formatters/__init__.py
+++ b/venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/formatters/__init__.py
@@ -91,1 +91,0 @@
-this method is equivalent to running ``eval()`` on the input file. The formatter is
@@ -103,1 +102,0 @@
-exec(f.read(), custom_namespace)
diff --git a/venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/lexers/__init__.py b/venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/lexers/__init__.py
--- a/venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/lexers/__init__.py
+++ b/venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/lexers/__init__.py
@@ -154,1 +154,0 @@
-exec(f.read(), custom_namespace)
diff --git a/venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/packages/six.py b/venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/packages/six.py
--- a/venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/packages/six.py
+++ b/venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/packages/six.py
@@ -787,1 +787,0 @@
-exec ("""exec _code_ in _globs_, _locs_""")

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.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: data-query: Hidden zero-width characters detected (KillerSkills verdict caution 70)

## 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 70/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/data-query/1.0.0

## Findings with a location
- `venv_dm/lib/python3.14/site-packages/pip/_internal/utils/unpacking.py:272` · Hidden zero-width characters detected — venv_dm/lib/python3.14/site-packages/pip/_internal/utils/unpacking.py:272 · Hidden zero-width characters detected — may conceal content
- `venv_dm/lib/python3.14/site-packages/pip/_vendor/pkg_resources/__init__.py:1725` · Python exec or eval of computed code — venv_dm/lib/python3.14/site-packages/pip/_vendor/pkg_resources/__init__.py:1725 · Python exec or eval of computed code
- `venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/util/url.py:148` · URL with embedded credentials — venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/util/url.py:148 · URL with embedded credentials — may be phishing or credential leaking
- `venv_dm/lib/python3.14/site-packages/pip/_vendor/pkg_resources/__init__.py:1714` · Python exec or eval of computed code — venv_dm/lib/python3.14/site-packages/pip/_vendor/pkg_resources/__init__.py:1714 · Python exec or eval of computed code
- `venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/formatters/__init__.py:103` · Python exec or eval of computed code — venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/formatters/__init__.py:103 · Python exec or eval of computed code
- `venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/lexers/__init__.py:154` · Python exec or eval of computed code — venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/lexers/__init__.py:154 · Python exec or eval of computed code
- `venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/formatters/__init__.py:91` · Python exec or eval of computed code — venv_dm/lib/python3.14/site-packages/pip/_vendor/pygments/formatters/__init__.py:91 · Python exec or eval of computed code
- `venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/packages/six.py:787` · Python exec or eval of computed code — venv_dm/lib/python3.14/site-packages/pip/_vendor/urllib3/packages/six.py:787 · Python exec or eval of computed code

## Proposed change
The attached patch removes the 8 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.