Is Archify safe?
- Node.js shell/command execution
- Node.js filesystem read
- Node.js filesystem write/delete
repo is an AI ai_component analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 4 risky constructs are reported for review. It can: filesystem read, filesystem write, network egress and 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 Archify'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 (4)
The component can run operating-system commands or spawn processes.
import { spawnSync } from 'node:child_process';return spawnSync(process.execPath, args, {import { spawn } from 'node:child_process';child = spawn(process.execPath, [checkerPath, String(deadlineNs)], {import { execFile } from 'node:child_process';import { spawnSync } from 'node:child_process';result = spawn(opener.command, opener.args(target), spawnOptions);
import { spawn } from 'node:child_process';child = spawn(process.execPath, args, {import { spawn } from 'node:child_process';import { spawnSync } from 'node:child_process';const result = spawnSync('git', ['--no-replace-objects', '-C', repoRoot, ...args], {const result = spawnSync('git', ['--no-replace-objects', '-C', repoRoot, 'cat-file', mode], {import { execFileSync } from 'node:child_process';import { spawnSync } from 'node:child_process';const result = spawnSync(process.execPath, [
import { spawn, spawnSync } from 'node:child_process';return spawnSync(invocation.command, invocation.args, options);
return spawn(invocation.command, invocation.args, options);
import { execFileSync } from 'node:child_process';import { spawn, spawnSync } from 'node:child_process';const result = spawnSync('sh', ['-c', 'command -v "$1"', 'archify-showcase', command], {const chrome = spawn(chromePath, chromeArgs, { stdio: ['ignore', 'ignore', 'pipe', 'pipe', 'pipe'] });const result = spawnSync(ffmpeg, [
import { execFileSync } from 'node:child_process';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.
artifact = fs.readFileSync(outputPath);
artifact ||= fs.readFileSync(outputPath);
baseBuffer = fs.readFileSync(basePath);
headBuffer = fs.readFileSync(headPath);
const artifact = fs.readFileSync(htmlCandidate);
specification = fs.readFileSync(inputPath);
const renderedCandidate = fs.readFileSync(candidatePath);
artifact = fs.readFileSync(candidatePath);
const source = JSON.parse(fs.readFileSync(path.resolve(input), 'utf8'));
sourceBytes = fs.readFileSync(sourcePath);
const migrationArtifact = fs.readFileSync(artifactPath);
const currentSourceBytes = fs.readFileSync(sourcePath);
specification = fs.readFileSync(inputPath);
const engineeringProfile = engineeringProfileFromArtifact(fs.readFileSync(out));
const bytes = fs.readFileSync(file);
delivery = JSON.parse(fs.readFileSync(deliveryPath, 'utf8'));
const bytes = fs.readFileSync(inputPath);
const source = JSON.parse(fs.readFileSync(inputPath, 'utf8'));
input = fs.readFileSync(inputPath, 'utf8');
const template = fs.readFileSync(path.join(skillRoot, 'assets/template.html'), 'utf8');
const bytes = fs.readFileSync(htmlPath);
const catalog = JSON.parse(fs.readFileSync(catalogPath, 'utf8'));
const simpleIconsVersion = JSON.parse(fs.readFileSync(
? fs.readFileSync(outputPath, 'utf8').replace(/\r\n?/g, '\n')
ajv.addSchema(JSON.parse(fs.readFileSync(path.join(schemasDir, 'common.schema.json'), 'utf8')));
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 writes or deletes files on disk.
fs.writeFileSync(descriptor, recoveryReceipt);
fs.writeFileSync(ownedLock.descriptor, lockReceipt);
fs.writeFileSync(temporary, serialized, { flag: 'wx' });fs.writeFileSync(candidate, serialized, { flag: 'wx' });fs.writeFileSync(snapshotPath, buffer, { flag: 'wx' });fs.writeFileSync(canonicalBaseInput, canonicalBaseBytes);
fs.writeFileSync(canonicalHeadInput, canonicalHeadBytes);
fs.writeFileSync(htmlCandidate, html);
fs.writeFileSync(receiptCandidate, receiptBytes);
fs.writeFileSync(specificationSnapshotPath, specification, { flag: 'wx' });fs.writeFileSync(provenanceCandidatePath, provenanceBytes, { flag: 'wx' });fs.writeFileSync(candidatePath, destinationBytes, { flag: 'wx' });fs.writeFileSync(snapshot, specification, { flag: 'wx' });fs.rmSync(tmp, { recursive: true, force: true });fs.writeFileSync(temporary, serialized, { flag: 'wx' });fs.writeFileSync(descriptor, artifact);
fs.writeFileSync(snapshotPath, digest.bytes, { flag: 'wx', mode: 0o600 });fs.writeFileSync(descriptor, contents);
else fs.writeFileSync(screenshotPath, screenshot, { flag: 'wx' });fs.rmSync(this.profileRoot, { recursive: true, force: true });fs.unlinkSync(quarantineFile);
fs.unlinkSync(quarantineFile);
fs.writeFileSync(descriptor, html);
fs.unlinkSync(quarantinePath);
mutate: () => fs.rm(resolved, options),
Why it matters: Usually legitimate, but worth confirming the paths can't be controlled by untrusted input.
Fix: Confirm which files are written/deleted and that paths cannot be influenced by untrusted input.
The component makes outbound network requests.
import http from 'node:http';
import http from 'node:http';
import https from 'node:https';
const response = await fetch(new URL('/state', url));const response = await fetch(`https://api.github.com${route}`, {const response = await fetch(url, { signal: AbortSignal.timeout(10000) });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.
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 →