critical
suspicious.dynamic_code_execution
- Location
- scripts/sheetsmith.py:123
- Finding
- Dynamic code execution detected.
Sheetsmith
AdvisoryAudited by Static analysis on May 10, 2026.
Overview
Detected: suspicious.dynamic_code_execution
Findings (1)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
NoteHigh Confidence
ASI05: Unexpected Code ExecutionWhat this means
If a user or agent runs a bad or untrusted expression, the spreadsheet output could be wrong or unexpectedly modified.
Why it was flagged
Transform expressions supplied on the command line are dynamically evaluated by pandas; this is central to the skill's stated purpose, but untrusted expressions could cause unintended computation or data changes.
Skill content
df.eval(expr, inplace=True, engine="python")
Recommendation
Review expressions before running them, prefer simple arithmetic/column formulas, and do not copy formulas from untrusted files or messages without checking them.
NoteHigh Confidence
ASI02: Tool Misuse and ExploitationWhat this means
A mistaken path or --inplace use could overwrite a spreadsheet the user meant to preserve.
Why it was flagged
The skill intentionally supports reading user-selected paths and overwriting the source file when explicitly requested; this is disclosed and purpose-aligned, but users should notice the mutation capability.
Skill content
reference it via a full path ... pass `--inplace` to overwrite the source file
Recommendation
Use --output to create a new file by default, keep a raw backup, and reserve --inplace for cases where overwriting is clearly intended.
NoteMedium Confidence
ASI06: Memory and Context PoisoningWhat this means
If enabled, details about handled datasets may persist beyond the immediate task.
Why it was flagged
The README describes optional persistent memory logging of dataset activity; no code forces this behavior, but users should understand it could retain dataset names or workflow details.
Skill content
If you want me to keep a log of every dataset I touched, I can update `memory` entries as part of the workflow.
Recommendation
Only request memory logging for non-sensitive workflows, and specify exactly what should or should not be remembered.