Skip to main content
SkillTotal

Is Archify safe?

What Archify does

Archify is an agent skill that turns a description, plan or codebase into an interactive, self-contained HTML visual, such as an architecture map or workflow. It is published in the tt-a1i/archify repository and needs Node.js 18 or later. It runs a Node CLI that reads JSON specs and writes HTML files; its preview mode serves on a random 127.0.0.1 port, and deliver --open launches the generated file. Before installing, prefer a project-level install over the global option if you only need it in one repository, and review generated HTML before sharing it, since outputs can link to external websites.

Partially analyzed - 1 code file not read (1 minified)
Notable — review in context (a capability is not a malicious indicator):
  • Node.js shell/command execution
  • Node.js filesystem read
  • Node.js filesystem write/delete

What to do: Nothing here argues against installing it. Grant the capabilities it lists only if you expect the tool to need them.

Archify is an agent skill analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators. It can: filesystem read, filesystem write, mcp tools detected, network egress and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).

archify-repository

GitHub repository, read as an npm package · https://github.com/tt-a1i/archify
LOW
0
/ 100 risk score
Snapshot · scanned Nov 13, 2026 · archify-repository@e378488 · engine 1.1.0 / ruleset 100

Get notified when this component changes

Change alerts aren't live yet. Leave your email and we'll let you know when they launch. We use it only for this and delete it on request.

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.

Capabilities — what this component can do (not a risk score):
filesystem readfilesystem writemcp tools detectednetwork egressshell execution

Behavioral traits

How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.

Tool surface
Tool Usage
Execution authority
Tool Access Control / Direct Tool Access
Filesystem reach
Tool Execution Context
Network egress
Interaction & Communication / Direct Communication

Findings (5)

CapabilityNode.js shell/command executionnot scored · severity highST-SHELL-NODE

The component can run operating-system commands or spawn processes.

import { spawn, execFileSync } from 'node:child_process';
const child = spawn(process.execPath, [path.join(tree, 'bin/archify.mjs'), 'render', entry.type, entry.file, output, '--quality', quality], { stdio: ['ignore', 'pipe', 'pipe'] });
import { execFileSync } from 'node:child_process';
import { spawnSync } from 'node:child_process';
const result = 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 run=spawnSync(process.execPath,[fileURLToPath(new URL('../scripts/check-render-output.mjs',import.meta.url)),artifactPath],{encoding:'utf8',maxBuffer:8*1024*1024,timeout:60000});
import { execFile } from 'node:child_process';
import { spawnSync } from 'node:child_process';
const result = spawnSync('git', ['--no-replace-objects', '-C', repoRoot, ...args], { maxBuffer: limit });
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 { execFileSync } from 'node:child_process';
import { spawnSync } from 'node:child_process';
const result = spawnSync(process.execPath, [

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.

CapabilityNode.js filesystem readnot scored · severity mediumST-FS-NODE-READ

The component reads files from disk.

const recorded = fs.existsSync(path.join(root, 'round.json')) ? JSON.parse(fs.readFileSync(path.join(root, 'round.json'), 'utf8')) : {};
const exported = JSON.parse(fs.readFileSync(file, 'utf8'));
return files[0] ? JSON.parse(fs.readFileSync(files[0], 'utf8')) : null;
const index = fs.existsSync(path.join(bench, 'index.json')) ? JSON.parse(fs.readFileSync(path.join(bench, 'index.json'), 'utf8')) : {};
const inventory = entries.map(({ type, name, file }) => ({ type, name, sha256: crypto.createHash('sha256').update(fs.readFileSync(file)).digest('hex') }));
const document = JSON.parse(fs.readFileSync(entry.file, 'utf8'));
try { geometry = renderedSvgFingerprint(fs.readFileSync(output, 'utf8')); }
const { results } = JSON.parse(fs.readFileSync(path.join(target, 'replay.json'), 'utf8'));
const bytes = fs.existsSync(pending) ? fs.readFileSync(pending) : Buffer.alloc(0);
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);
captureDeliveryStagingFile(preparedBundlePath, artifactIdentity(fs.readFileSync(preparedBundlePath)));
const renderedCandidate = fs.readFileSync(candidatePath);
artifact = fs.readFileSync(candidatePath);
const source = JSON.parse(fs.readFileSync(path.resolve(input), 'utf8'));
preparedExplainer = await prepareExplainerInput(fs.readFileSync(path.resolve(input)), path.resolve(input), { repoRoot: repoArgs.repoRoot, quality: qualityArgs.quality || 'showcase', writingMode: writingArgs.writingMode });
sourceBytes = fs.readFileSync(sourcePath);
const migrationArtifact = fs.readFileSync(artifactPath);
const currentSourceBytes = fs.readFileSync(sourcePath);
specification = fs.readFileSync(inputPath);
const engineeringProfile = engineeringProfileFromArtifact(fs.readFileSync(out));

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.

CapabilityNode.js filesystem write/deletenot scored · severity mediumST-FS-NODE-WRITE

The component writes or deletes files on disk.

if (args.includes('--dump')) fs.writeFileSync(path.join(root, `${type}.trace.txt`), stats.dump.join('\n\n'));
if (stats.firstDraft) fs.writeFileSync(path.join(root, type, 'first-draft.json'), `${JSON.stringify(stats.firstDraft, null, 2)}\n`);
fs.writeFileSync(path.join(bench, type, `${round}.json`), `${JSON.stringify(benchmarkDocument(stats.firstDraft, round), null, 2)}\n`);
fs.writeFileSync(path.join(bench, 'index.json'), `${JSON.stringify(index, null, 2)}\n`);
fs.writeFileSync(path.join(root, 'tuning-summary.json'), `${JSON.stringify(summary, null, 2)}\n`);
fs.writeFileSync(path.join(out, 'replay.json'), `${JSON.stringify({ schemaVersion: 1, base, head, bench, provenance, results }, null, 2)}\n`);
fs.writeFileSync(path.join(root, 'round.json'), `${JSON.stringify(record, null, 2)}\n`);
fs.writeFileSync(path.join(root, 'prompts.json'), `${JSON.stringify(prompts, null, 2)}\n`);
fs.rmSync(staging, { recursive: true, force: true });
fs.writeFileSync(path.join(shots, 'capture.json'), `${JSON.stringify({ schemaVersion: 1, replay: path.join(target, 'replay.json'), viewport: { width: 1440, height }, theme: 'light', ...(cleanupFailure ? { cleanupFailure } : {}), captures }, …
fs.writeFileSync(path.join(shots, 'index.html'), `<!doctype html><meta charset="utf-8"><title>Replay shots</title>
fs.writeFileSync(descriptor, recoveryReceipt);
fs.writeFileSync(ownedLock.descriptor, lockReceipt);
fs.rmdirSync(directory);
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' });

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.

CapabilityNode.js network egressnot scored · severity mediumST-NET-NODE

The component makes outbound network requests.

import http from 'node:http';
import { lookup } from 'node:dns/promises';
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.

CapabilityMCP tool surface detectednot scored · severity lowST-MCP-DETECTED

An MCP tool surface (manifest or tool definitions) was found.

Why it matters: Just context — review which tools it offers and their permissions.

Fix: Review the declared MCP tools and their permissions.

How attackers abuse these capabilities

Interactive labs on the attack class behind the rules above. They show the technique, not anything found in Archify.

Maintain Archify?

Check the next package before your agent installs it

The free Claude Code plugin scans each npm, PyPI or MCP package with this report's open-source engine before the install command runs. It runs on your machine and needs no account.

Check your own component

Run the same evidence-backed scan on any MCP server, agent skill, or package.

Scan your own component

How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →