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. 77 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 22 caught lines
Download .patchdiff --git a/src/stratum_mcp/executor.py b/src/stratum_mcp/executor.py
--- a/src/stratum_mcp/executor.py
+++ b/src/stratum_mcp/executor.py
@@ -301,1 +301,0 @@
-return bool(eval(
@@ -352,1 +351,0 @@
-value = eval(code, {"__builtins__": {}, **_ENSURE_BUILTINS}, {"result": result})
@@ -391,1 +389,0 @@
-return eval(code, {"__builtins__": {}, **_ENSURE_BUILTINS}, {bind: value})
@@ -449,1 +446,0 @@
-return bool(eval(
@@ -679,1 +675,0 @@
-return bool(eval(code, {"__builtins__": {}, "None": None, "True": True, "False": False,
diff --git a/src/stratum_mcp/skills/stratum-onboard/SKILL.md b/src/stratum_mcp/skills/stratum-onboard/SKILL.md
--- a/src/stratum_mcp/skills/stratum-onboard/SKILL.md
+++ b/src/stratum_mcp/skills/stratum-onboard/SKILL.md
@@ -3,1 +3,0 @@
---- name: stratum-onboard description: Read a codebase cold and write a project-specific MEMORY.md from scratch — architecture patterns, test conventions, module constraints, kno…
@@ -22,1 +21,0 @@
-5. Write conclusions to `MEMORY.md` at `.claude/memory/MEMORY.md` (create if missing)
@@ -169,1 +167,0 @@
-…rns. **After `stratum_audit`:** The `write_memory` step produces the entries — write them to `.claude/memory/MEMORY.md` (create directory and file if missing). Tag each entry with the skill it appli…
diff --git a/src/stratum_mcp/skills/stratum-debug/SKILL.md b/src/stratum_mcp/skills/stratum-debug/SKILL.md
--- a/src/stratum_mcp/skills/stratum-debug/SKILL.md
+++ b/src/stratum_mcp/skills/stratum-debug/SKILL.md
@@ -198,1 +198,0 @@
-**After the fix:** Append to `MEMORY.md`:
diff --git a/src/stratum_mcp/skills/stratum-migrate/SKILL.md b/src/stratum_mcp/skills/stratum-migrate/SKILL.md
--- a/src/stratum_mcp/skills/stratum-migrate/SKILL.md
+++ b/src/stratum_mcp/skills/stratum-migrate/SKILL.md
@@ -151,1 +151,0 @@
-**After migration:** Append to `MEMORY.md`:
diff --git a/src/stratum_mcp/skills/stratum-review/SKILL.md b/src/stratum_mcp/skills/stratum-review/SKILL.md
--- a/src/stratum_mcp/skills/stratum-review/SKILL.md
+++ b/src/stratum_mcp/skills/stratum-review/SKILL.md
@@ -179,1 +179,0 @@
-…ule with known fragility, a class of issue this project tends to have)? If yes, append a one-liner to `MEMORY.md`: ``` [stratum-review] <pattern> — e.g. "auth middleware bypasses rate limitin…
diff --git a/src/stratum_mcp/skills/stratum-speckit/SKILL.md b/src/stratum_mcp/skills/stratum-speckit/SKILL.md
--- a/src/stratum_mcp/skills/stratum-speckit/SKILL.md
+++ b/src/stratum_mcp/skills/stratum-speckit/SKILL.md
@@ -287,1 +287,0 @@
-**After Phase 4 `stratum_audit`:** For each step with `attempts > 1`, ask: does the retry reveal a project-specific pattern worth capturing? Append one-liners to `MEMORY.md`:
diff --git a/src/stratum_mcp/skills/stratum-test/SKILL.md b/src/stratum_mcp/skills/stratum-test/SKILL.md
--- a/src/stratum_mcp/skills/stratum-test/SKILL.md
+++ b/src/stratum_mcp/skills/stratum-test/SKILL.md
@@ -144,1 +144,0 @@
-**After `stratum_audit`:** If any step needed retries, append to `MEMORY.md`:
diff --git a/src/stratum_mcp/skills/stratum-refactor/SKILL.md b/src/stratum_mcp/skills/stratum-refactor/SKILL.md
--- a/src/stratum_mcp/skills/stratum-refactor/SKILL.md
+++ b/src/stratum_mcp/skills/stratum-refactor/SKILL.md
@@ -158,1 +158,0 @@
-**After each extraction:** If a step needed retries because of an unexpected dependency or import constraint, append to `MEMORY.md`:
diff --git a/src/stratum_mcp/skills/stratum-feature/SKILL.md b/src/stratum_mcp/skills/stratum-feature/SKILL.md
--- a/src/stratum_mcp/skills/stratum-feature/SKILL.md
+++ b/src/stratum_mcp/skills/stratum-feature/SKILL.md
@@ -218,1 +218,0 @@
-…ious coupling, a test convention, an invariant that must be preserved)? If yes, append a one-liner to `MEMORY.md`: ``` [stratum-feature] tests use factory_boy fixtures, not pytest fixtures — …
diff --git a/src/stratum_mcp/hooks/stratum-session-stop.sh b/src/stratum_mcp/hooks/stratum-session-stop.sh
--- a/src/stratum_mcp/hooks/stratum-session-stop.sh
+++ b/src/stratum_mcp/hooks/stratum-session-stop.sh
@@ -2,1 +2,0 @@
-# Stratum hook (T2-M3): append a timestamped summary note to MEMORY.md at
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -70,1 +70,0 @@
-| `/stratum-onboard` | Read a new codebase cold and write project-specific `MEMORY.md` |
diff --git a/PKG-INFO b/PKG-INFO
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -95,1 +95,0 @@
-| `/stratum-onboard` | Read a new codebase cold and write project-specific `MEMORY.md` |
diff --git a/src/stratum_mcp/server.py b/src/stratum_mcp/server.py
--- a/src/stratum_mcp/server.py
+++ b/src/stratum_mcp/server.py
@@ -4624,1 +4624,0 @@
-"""Write .claude/mcp.json and append Stratum block to CLAUDE.md."""
@@ -4688,1 +4687,0 @@
-changed.append("CLAUDE.md")
@@ -4692,1 +4690,0 @@
-changed.append("CLAUDE.md")
@@ -4804,1 +4801,0 @@
-removed.append("CLAUDE.md")
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.114. 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: stratum-mcp: Python exec or eval of computed code (KillerSkills verdict caution 77)
## 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 77/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/stratum-mcp/0.2.114 ## Findings with a location - `src/stratum_mcp/executor.py:391` · Python exec or eval of computed code — src/stratum_mcp/executor.py:391 · Python exec or eval of computed code - `src/stratum_mcp/executor.py:449` · Python exec or eval of computed code — src/stratum_mcp/executor.py:449 · Python exec or eval of computed code - `src/stratum_mcp/skills/stratum-onboard/SKILL.md:169` · Instructs the agent to modify its persistent memory or instruction files — src/stratum_mcp/skills/stratum-onboard/SKILL.md:169 · Instructs the agent to modify its persistent memory or instruction files - `src/stratum_mcp/skills/stratum-debug/SKILL.md:198` · Instructs the agent to modify its persistent memory or instruction files — src/stratum_mcp/skills/stratum-debug/SKILL.md:198 · Instructs the agent to modify its persistent memory or instruction files - `src/stratum_mcp/skills/stratum-onboard/SKILL.md:22` · Instructs the agent to modify its persistent memory or instruction files — src/stratum_mcp/skills/stratum-onboard/SKILL.md:22 · Instructs the agent to modify its persistent memory or instruction files - `src/stratum_mcp/skills/stratum-migrate/SKILL.md:151` · Instructs the agent to modify its persistent memory or instruction files — src/stratum_mcp/skills/stratum-migrate/SKILL.md:151 · Instructs the agent to modify its persistent memory or instruction files - `src/stratum_mcp/skills/stratum-review/SKILL.md:179` · Instructs the agent to modify its persistent memory or instruction files — src/stratum_mcp/skills/stratum-review/SKILL.md:179 · Instructs the agent to modify its persistent memory or instruction files - `src/stratum_mcp/skills/stratum-onboard/SKILL.md:3` · Instructs the agent to modify its persistent memory or instruction files — src/stratum_mcp/skills/stratum-onboard/SKILL.md:3 · Instructs the agent to modify its persistent memory or instruction files - `src/stratum_mcp/executor.py:352` · Python exec or eval of computed code — src/stratum_mcp/executor.py:352 · Python exec or eval of computed code - `src/stratum_mcp/skills/stratum-speckit/SKILL.md:287` · Instructs the agent to modify its persistent memory or instruction files — src/stratum_mcp/skills/stratum-speckit/SKILL.md:287 · Instructs the agent to modify its persistent memory or instruction files - `src/stratum_mcp/skills/stratum-test/SKILL.md:144` · Instructs the agent to modify its persistent memory or instruction files — src/stratum_mcp/skills/stratum-test/SKILL.md:144 · Instructs the agent to modify its persistent memory or instruction files - `src/stratum_mcp/executor.py:679` · Python exec or eval of computed code — src/stratum_mcp/executor.py:679 · Python exec or eval of computed code ## Proposed change The attached patch removes the 22 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 smartmemory/stratum --clone && cd stratum curl -s https://killerskills.ai/skills/pypi/stratum-mcp/0.2.114/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.2.114 && git commit -am "stratum-mcp: Python exec or eval of computed code" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/stratum-mcp/0.2.114/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.