processes
Manages background jobs and long-running processes with commands for spawning, managing, and logging tasks efficiently.
Install this skill
Security score
The processes skill was audited on Feb 22, 2026 and we found 26 security issues across 2 threat categories, including 4 high-severity. Review the findings below before installing.
Categories Tested
Security Issues
Direct command execution function call
| 76 | const job = await processes.spawn({ |
Direct command execution function call
| 86 | const job = await processes.spawn({ |
Direct command execution function call
| 215 | const job = await processes.spawn({ |
Direct command execution function call
| 229 | const job = await processes.spawn({ |
Template literal with variable interpolation in command context
| 82 | console.log(`Job ID: ${job.id}`); |
Template literal with variable interpolation in command context
| 83 | console.log(`PID: ${job.pid}`); |
Template literal with variable interpolation in command context
| 117 | console.log(`${job.id}: ${job.name}`); |
Template literal with variable interpolation in command context
| 118 | console.log(` Status: ${job.status}`); // 'running' | 'stopped' | 'failed' | 'completed' |
Template literal with variable interpolation in command context
| 119 | console.log(` PID: ${job.pid}`); |
Template literal with variable interpolation in command context
| 120 | console.log(` Started: ${job.startedAt}`); |
Template literal with variable interpolation in command context
| 121 | console.log(` Memory: ${job.memoryMB}MB`); |
Template literal with variable interpolation in command context
| 122 | console.log(` CPU: ${job.cpuPercent}%`); |
Template literal with variable interpolation in command context
| 131 | console.log(`Status: ${status.status}`); |
Template literal with variable interpolation in command context
| 132 | console.log(`Exit code: ${status.exitCode}`); |
Template literal with variable interpolation in command context
| 133 | console.log(`Runtime: ${status.runtimeMs}ms`); |
Template literal with variable interpolation in command context
| 134 | console.log(`Restarts: ${status.restarts}`); |
Template literal with variable interpolation in command context
| 135 | console.log(`Memory: ${status.memoryMB}MB`); |
Template literal with variable interpolation in command context
| 136 | console.log(`CPU: ${status.cpuPercent}%`); |
Template literal with variable interpolation in command context
| 154 | stream.on('exit', (code) => console.log(`Exit: ${code}`)); |
Template literal with variable interpolation in command context
| 180 | console.log(`Job started: ${job.name}`); |
Template literal with variable interpolation in command context
| 184 | console.log(`Job stopped: ${job.name} (code: ${job.exitCode})`); |
Template literal with variable interpolation in command context
| 188 | console.error(`Job failed: ${job.name}`, error); |
Template literal with variable interpolation in command context
| 192 | console.log(`[${job.name}] ${type}: ${data}`); |
Template literal with variable interpolation in command context
| 223 | console.log(`Backtest complete: ${result.exitCode === 0 ? 'success' : 'failed'}`); |
Access to .env file
| 56 | env: process.env, |
Access to .env file
| 93 | ...process.env, |