registry / @netnodeag/kraftwerk / 0.10.0
@netnodeag/kraftwerk@0.10.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 lifecycle script is a publisher-side build hook, and the inspected process and remote-repository operations are tied to workflow use. The source reviewed did not establish concrete malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user sends a chat message, invokes a workflow, or selects a remote repository through the CLI.
Impact
No unconsented credential transfer, installation mutation, or other attack effect was established.
Mechanism
The package forwards supplied requests to an agent or workflow runner; optional Docker and SSH behavior is configured through run options.
AI rationale
The lifecycle script is a publisher-side build hook, and the inspected process and remote-repository operations are tied to workflow use. The source reviewed did not establish concrete malicious behavior.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines a prepublishOnly build command, with no preinstall, install, or postinstall hook.
- The inspector sends user-entered chat text to its local chat API.
- The inspector runner launches a workflow with the name and request supplied to it.
- Chat turns start from supplied user text; automatic permission approval is limited to scheduled team sessions.
- Remote repositories are resolved through the CLI's explicit --from option.
- Docker runs mount the selected workflow and pass configured runner environment values; SSH access is conditional on the SSH option.
Evidence against
- The inspected child-process and network behavior supports workflow execution and explicitly selected remote repositories; it does not establish install-time execution or unconsented data transfer.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
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.10.0.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.10.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.