registry / @netnodeag/kraftwerk / 0.9.0
@netnodeag/kraftwerk@0.9.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 lifecycle hook, and inspected network and process execution paths are tied to explicit user actions. The scanner signals correspond to build, remote workflow, inspector, and runner functionality; no concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user supplies a remote with --from, submits a workflow request, or sends a chat message.
Impact
No harmful impact from an automatic or unconsented action was established.
Mechanism
The CLI fetches the supplied remote; the inspector passes a supplied workflow request to its runner; submitted chat text starts backend work.
AI rationale
The manifest has no install lifecycle hook, and inspected network and process execution paths are tied to explicit user actions. The scanner signals correspond to build, remote workflow, inspector, and runner functionality; no concrete attack behavior was found.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares a prepublishOnly build command and no preinstall, install, or postinstall hook.
- Remote cloning is reached through the CLI's explicit --from option and uses the supplied remote.
- The inspector creates chats through its UI; chat backend work starts after a user message is submitted.
- The inspector starts a workflow only after a request is supplied, then passes that workflow and request to npx kraftwerk run.
- The Docker runner mounts the selected workflow read-only.
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.9.0.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.9.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.