Is Awesome Seedance safe?
- Node.js shell/command execution
- Python filesystem read
- Node.js network egress
What to do: Nothing here argues against installing it. Grant the capabilities it lists only if you expect the tool to need them.
Awesome Seedance is an npm package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators. It can: filesystem read, network egress and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
awesome-seedance 0.3.0
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of Awesome Seedance's authors. Report a false positive.
Behavioral traits
How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.
Findings (3)
The component can run operating-system commands or spawn processes.
import { execFileSync } from "node:child_process";import { spawn, spawnSync } from "node:child_process";const r = spawnSync(cmd, argv, { cwd: ROOT, encoding: "utf8", maxBuffer: 64 * 1024 * 1024, ...opts });const child = spawn("claude", ["-p", "--model", MODEL, "--output-format", "json"], { cwd, stdio: ["pipe", "pipe", "pipe"] });spawnSync("osascript", ["-e", `display notification "写入 ${Object.keys(report.assign).length} 条，留到下轮 ${report.deferred.length} 条。${title}" with title "awesome-seedance 每周归类"`]);Why it matters: Powerful and often legitimate — confirm the commands aren't built from untrusted input.
Fix: Confirm the command and its arguments are fully controlled and not derived from untrusted input; prefer execFile with an argument array.
The component reads files from disk.
plan = json.loads(Path(sys.argv[1]).read_text(encoding="utf-8"))
Why it matters: Usually legitimate, but worth confirming it can't be steered into reading sensitive files.
Fix: Confirm which files are read and that paths cannot be influenced by untrusted input to reach sensitive locations.
The component makes outbound network requests.
const res = await fetch(url);
const res = await fetch(url, { headers: { "user-agent": "awesome-seedance/site-stats" } });const res = await fetch(`https://goodcase.ai/skills/${skill.siteSlug}`, { headers: { "user-agent": "awesome-seedance/site-stats" } });Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.
Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.
How attackers abuse these capabilities
Interactive labs on the attack class behind the rules above. They show the technique, not anything found in Awesome Seedance.
Check your own component
Run the same evidence-backed scan on any MCP server, agent skill, or package.
Scan your own componentHow we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →