Scan Report
5 /100
jianying-auto-editor
Automate Jianying draft generation from local media plus a cloud editing API
Jianying video editor automation skill with clean implementation using only Node.js built-in modules, no shell execution, and well-scoped file/network permissions. The hardcoded IP in example config is a placeholder for users to replace.
Safe to install
Skill is safe to use. Users should replace the example API endpoint with their own cloud service. Consider documenting credential handling best practices.
Findings 3 items
| Severity | Finding | Location |
|---|---|---|
| Info | No external dependencies | package.json:8 |
| Info | Clean error handling with best-effort fallback | scripts/index.js:271 |
| Low | Placeholder IP in example config | examples/config.example.json:2 |
| Resource | Declared | Inferred | Status | Evidence |
|---|---|---|---|---|
| Filesystem | WRITE | WRITE | ✓ Aligned | scripts/index.js:156-158 writes draft-meta.json, draft-content.json, execution-r… |
| Filesystem | READ | READ | ✓ Aligned | scripts/index.js:97-142 scans material_path recursively for media files |
| Network | READ | READ | ✓ Aligned | scripts/index.js:179-203 uses native fetch API for GET/POST to configured cloud … |
| Shell | NONE | NONE | — | No subprocess, exec, or shell command invocations found in codebase |
1 High 3 findings
High IP Address 硬编码 IP 地址
43.137.46.105 examples/config.example.json:2 Medium External URL 外部 URL
https://api.example.com README.md:20 Medium External URL 外部 URL
http://43.137.46.105:8787 examples/config.example.json:2 File Tree
8 files · 22.3 KB · 749 lines JavaScript 1f · 394L
JSON 3f · 178L
Markdown 2f · 173L
YAML 1f · 4L
├─
▾
agents
│ └─
openai.yaml
YAML
├─
▾
assets
│ └─
icon.svg
├─
▾
examples
│ └─
config.example.json
JSON
├─
▾
scripts
│ └─
index.js
JavaScript
├─
manifest.json
JSON
├─
package.json
JSON
├─
README.md
Markdown
└─
SKILL.md
Markdown
Security Positives
✓ No shell execution or subprocess invocations
✓ No credential harvesting from environment variables
✓ No access to sensitive paths (~/.ssh, ~/.aws, .env)
✓ No eval(), Function(), or dynamic code execution
✓ No base64-encoded payloads piped to shell
✓ No remote script download/execution (curl|bash, wget|sh)
✓ No hidden instructions in comments or documentation
✓ Uses native fetch API with proper timeout and signal handling
✓ No external npm dependencies - all built-in Node.js modules only
✓ API key properly scoped to Authorization Bearer header
✓ Config validation prevents missing required fields