T09 · Insecure Skill Coding Practices
- Location
scripts/cli.py:10- Finding
Path Traversal in Dynamic Script Dispatch Enables Local Python Code Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent local novel-writing tool, but its command launcher can be abused to run unintended local Python files.
Review before installing. Use only documented CLI aliases, avoid arbitrary command names or --scripts values, run it in a dedicated project/virtual environment, and pin optional dependencies such as jieba before installation. Expect it to read manuscript files and create local reports, backups, config, and cache files.
scripts/cli.py:10Path Traversal in Dynamic Script Dispatch Enables Local Python Code Execution
README.md:95Unpinned Optional Dependency Installation Creates Supply-Chain Exposure
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
The manifest explicitly documents caching, file hashing, change scanning, SQLite state, and parallel script infrastructure, all of which are operational behaviors beyond a simple writing assistant. Because these capabilities interact with the local filesystem and persistent state, presenting the skill primarily as a novel-writing engine understates its automation footprint and can lead to over-trust and unintended execution.
No suspicious patterns detected.