Is Hue safe?
- Node.js shell/command execution
repo is an AI agent_skill analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 1 risky construct are reported for review. It can: shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
repo
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of Hue'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 (1)
The component can run operating-system commands or spawn processes.
import { spawnSync } from 'node:child_process';while ((m = re.exec(html))) blocks.push(m[1]);
const r = spawnSync('npx', ['--yes', 'js-yaml', file], { encoding: 'utf8' });while ((m = attrRe.exec(html))) {while ((m = scriptRe.exec(html))) {while ((lm = litRe.exec(m[1]))) {while ((m = re.exec(css))) {while ((cm = cre.exec(cleaned))) out.push({ selector: part, cls: cm[1] });while ((m = defRe.exec(content))) defined.add(m[1]);
while ((m = propRe.exec(content))) defined.add(m[1]);
while ((m = useRe.exec(content))) {while ((fm = fre.exec(val))) obj[fm[1]] = fm[2].trim().replace(/^["']|["']$/g, '');
while ((m = defRe.exec(css))) defs[m[1]] = m[2].trim();
while ((m = ruleRe.exec(css))) {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.
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 →