← codepathfinder@2.1.1

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. 68 · Caution

Evidence

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

Diff · removes 7 caught lines

Download .patch
diff --git a/codepathfinder/python_rule_meta.py b/codepathfinder/python_rule_meta.py
--- a/codepathfinder/python_rule_meta.py
+++ b/codepathfinder/python_rule_meta.py
@@ -361,1 +361,0 @@
-"The main sinks are eval() and evalsha() which run Lua scripts — injection-sensitive "
@@ -1045,1 +1044,0 @@
-"evaluator for literals only. The builtins eval() and exec() execute arbitrary Python "
@@ -1046,1 +1044,0 @@
-"code — RCE sinks on user input. compile() produces code objects that reach exec()."
@@ -1054,1 +1051,0 @@
-"description": "Safely evaluates Python literals (str, int, list, dict, tuple, bool, None). Sanitizer replacement for eval().",
@@ -1065,1 +1061,0 @@
-"signature": "eval(expression, globals=None, locals=None) -> Any",
@@ -1071,1 +1066,0 @@
-"signature": "exec(object, globals=None, locals=None) -> None",
diff --git a/setup.py b/setup.py
--- a/setup.py
+++ b/setup.py
@@ -11,1 +11,0 @@
-exec(line, version)

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

## 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 68/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/codepathfinder/2.1.1

## Findings with a location
- `codepathfinder/python_rule_meta.py:1045` · Python exec or eval of computed code — codepathfinder/python_rule_meta.py:1045 · Python exec or eval of computed code
- `codepathfinder/python_rule_meta.py:1046` · Python exec or eval of computed code — codepathfinder/python_rule_meta.py:1046 · Python exec or eval of computed code
- `setup.py:11` · Python exec or eval of computed code — setup.py:11 · Python exec or eval of computed code
- `codepathfinder/python_rule_meta.py:361` · Python exec or eval of computed code — codepathfinder/python_rule_meta.py:361 · Python exec or eval of computed code
- `codepathfinder/python_rule_meta.py:1071` · Python exec or eval of computed code — codepathfinder/python_rule_meta.py:1071 · Python exec or eval of computed code
- `codepathfinder/python_rule_meta.py:1054` · Python exec or eval of computed code — codepathfinder/python_rule_meta.py:1054 · Python exec or eval of computed code
- `codepathfinder/python_rule_meta.py:1065` · Python exec or eval of computed code — codepathfinder/python_rule_meta.py:1065 · Python exec or eval of computed code

## Proposed change
The attached patch removes the 7 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 shivasurya/code-pathfinder --clone && cd code-pathfinder
curl -s https://killerskills.ai/skills/pypi/codepathfinder/2.1.1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/2.1.1 && git commit -am "codepathfinder: Python exec or eval of computed code"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/codepathfinder/2.1.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.