← ztp@2.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. 54 · Caution

Evidence

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

Diff · removes 6 caught lines

Download .patch
diff --git a/tests/test_integration.py b/tests/test_integration.py
--- a/tests/test_integration.py
+++ b/tests/test_integration.py
@@ -35,1 +35,0 @@
-p.write_text("def malicious():\n    eval('1+1')")
@@ -94,1 +93,0 @@
-p.write_text("eval('evil');\ndocument.write('hacked');")
@@ -123,1 +121,0 @@
-(tmp_path / "test_mal.py").write_text("eval(x)")
diff --git a/scripts/shield_pro.py b/scripts/shield_pro.py
--- a/scripts/shield_pro.py
+++ b/scripts/shield_pro.py
@@ -158,1 +158,0 @@
-Helps reduce false positives for harmless dynamic execution like eval('1+1').
diff --git a/tests/test_shield.py b/tests/test_shield.py
--- a/tests/test_shield.py
+++ b/tests/test_shield.py
@@ -19,1 +19,0 @@
-source = "eval('1+1')\nos.system('ls')\nexec(user_input)"
@@ -87,1 +86,0 @@
-source = "eval('[1, 2, 3]')"

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.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: ztp: Python exec or eval of computed code (KillerSkills verdict caution 54)

## 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 54/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/ztp/2.0.0

## Findings with a location
- `tests/test_integration.py:123` · Python exec or eval of computed code — tests/test_integration.py:123 · Python exec or eval of computed code
- `scripts/shield_pro.py:158` · Python exec or eval of computed code — scripts/shield_pro.py:158 · Python exec or eval of computed code
- `tests/test_shield.py:19` · Python exec or eval of computed code — tests/test_shield.py:19 · Python exec or eval of computed code
- `tests/test_shield.py:87` · Python exec or eval of computed code — tests/test_shield.py:87 · Python exec or eval of computed code
- `tests/test_integration.py:35` · Python exec or eval of computed code — tests/test_integration.py:35 · Python exec or eval of computed code
- `tests/test_integration.py:94` · Python exec or eval of computed code — tests/test_integration.py:94 · Python exec or eval of computed code

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