registry / @netnodeag/kraftwerk / 0.13.0
@netnodeag/kraftwerk@0.13.0
Deterministic workflow-as-code framework: agents (persona + model + tools + harness) run in bounded phases on headless CLI harnesses (claude -p, codex exec, pi); code owns the control flow, envelopes + gates judge the results
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe manifest has no install hook; its prepublishOnly script builds the package. Inspected runtime capabilities are tied to user-invoked workflow, chat, remote-source, or sandbox operations, with no concrete attack behavior established.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user invokes the CLI or starts a workflow or chat through the inspector.
Impact
No unauthorized installation-time action, credential transfer to an unrelated recipient, or other concrete attack was established.
Mechanism
The package launches the selected workflow or agent backend; remote cloning uses a supplied --from source, and SSH forwarding requires the sandbox SSH option.
AI rationale
The manifest has no install hook; its prepublishOnly script builds the package. Inspected runtime capabilities are tied to user-invoked workflow, chat, remote-source, or sandbox operations, with no concrete attack behavior established.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines a prepublishOnly build command and no install lifecycle hook.
- The CLI launcher imports the package entrypoint when invoked; the inspector UI creates chats through its local API, and sessions pass posted user messages to an agent backend.
- Remote cloning is reached through the explicit --from option and uses the supplied repository specification.
- Docker and subprocess features support user-requested workflow runs; SSH forwarding is conditional on opts.ssh.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedPossibleObfuscationTelemetryUrlStrings
Source & flagged code
5 flaggeddist/remote.jsView file
1import { spawnSync } from "node:child_process";
L2: import { mkdir, stat } from "node:fs/promises";
High
bin/kraftwerk.jsView file
15if (existsSync(src) && process.env.KRAFTWERK_DIST !== "1") {
L16: const { register } = await import("tsx/esm/api");
L17: register();
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/kraftwerk.jsView on unpkg · L15dist/inspector/runner.jsView file
1import { spawn, spawnSync } from "node:child_process";
L2: import { mkdirSync, openSync, closeSync } from "node:fs";
...
L8: * Workflow trigger for the web UI. The inspector stays decoupled from the
L9: * framework runtime: it shells out to `npx kraftwerk run` in the consumer
L10: * project, detached, with a pre-chosen --run-id so the browser can jump to
Findings
1 Critical4 High4 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/runner/docker.js
HighChild Processdist/remote.js
HighShell
HighRuntime Package Installdist/inspector/runner.js
HighSemantic Analysis Limiteddist/inspector/chat/sessions.js
MediumDynamic Requirebin/kraftwerk.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to @netnodeag/kraftwerk@0.13.0.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.13.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.