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. 62 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 6 caught lines
Download .patchdiff --git a/nim_ensemble/cascade.py b/nim_ensemble/cascade.py
--- a/nim_ensemble/cascade.py
+++ b/nim_ensemble/cascade.py
@@ -55,1 +55,0 @@
-"cursor.execute", "eval(", "exec(", "import os", "subprocess",
diff --git a/tests/test_core.py b/tests/test_core.py
--- a/tests/test_core.py
+++ b/tests/test_core.py
@@ -221,1 +221,0 @@
-assert classify_task("Is this Python function safe? def foo(): eval(input())") == "code"
@@ -342,1 +341,0 @@
-code = "user_input = input(); exec(user_input)"
@@ -358,1 +356,0 @@
-question = "Is this Python code safe? def f(): eval(x)"
diff --git a/nim_ensemble/voter.py b/nim_ensemble/voter.py
--- a/nim_ensemble/voter.py
+++ b/nim_ensemble/voter.py
@@ -158,1 +158,0 @@
-pass
diff --git a/nim_ensemble/benchmark.py b/nim_ensemble/benchmark.py
--- a/nim_ensemble/benchmark.py
+++ b/nim_ensemble/benchmark.py
@@ -193,1 +193,0 @@
-eval(input("Enter command: "))
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 3.3.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: free-scaling: Python exec or eval of computed code (KillerSkills verdict caution 62)
## 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 62/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/free-scaling/3.3.1 ## Findings with a location - `nim_ensemble/cascade.py:55` · Python exec or eval of computed code — nim_ensemble/cascade.py:55 · Python exec or eval of computed code - `tests/test_core.py:358` · Python exec or eval of computed code — tests/test_core.py:358 · Python exec or eval of computed code - `nim_ensemble/voter.py:158` · Credential pass-through configuration — nim_ensemble/voter.py:158 · Credential pass-through configuration — agent relays sensitive credentials - `tests/test_core.py:342` · Python exec or eval of computed code — tests/test_core.py:342 · Python exec or eval of computed code - `nim_ensemble/benchmark.py:193` · Python exec or eval of computed code — nim_ensemble/benchmark.py:193 · Python exec or eval of computed code - `tests/test_core.py:221` · Python exec or eval of computed code — tests/test_core.py:221 · 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._
# or from a terminal, under your own account: gh repo fork isotrivial/free-scaling --clone && cd free-scaling curl -s https://killerskills.ai/skills/clawhub/free-scaling/3.3.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/3.3.1 && git commit -am "free-scaling: Python exec or eval of computed code" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/free-scaling/3.3.1/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.