← botmark-skill@2.20.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. 76 · Caution

Evidence

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

Diff · removes 2 caught lines

Download .patch
diff --git a/botmark_engine.py b/botmark_engine.py
--- a/botmark_engine.py
+++ b/botmark_engine.py
@@ -987,1 +987,0 @@
-block completion messages) breaks exec() output parsing and causes
@@ -1030,1 +1029,0 @@
-[BOTMARK_OWNER] to stdout would contaminate exec() output and crash

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

## 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 76/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/botmark-skill/2.20.0

## Findings with a location
- `botmark_engine.py:1030` · Python exec or eval of computed code — botmark_engine.py:1030 · Python exec or eval of computed code
- `botmark_engine.py:987` · Python exec or eval of computed code — botmark_engine.py:987 · Python exec or eval of computed code

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