registry / @netnodeag/kraftwerk / 0.10.2
@netnodeag/kraftwerk@0.10.2
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 reviewed runtime operations are tied to user-selected workflows, repositories or skill invocations. The scanner's execution and network indicators correspond to these framework functions; inspected source did not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
User runs a Kraftwerk command, selects a remote workflow, starts an inspector run, or invokes a chat skill.
Impact
No unconsented credential transfer, install-time mutation or other concrete attack was established.
Mechanism
The package launches the selected workflow or clones the caller-specified repository; the inspector bundle makes local API requests.
AI rationale
The manifest has no install lifecycle hook, and reviewed runtime operations are tied to user-selected workflows, repositories or skill invocations. The scanner's execution and network indicators correspond to these framework functions; inspected source did not establish malicious behavior.
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 only a prepublishOnly build hook; it has no preinstall, install or postinstall hook.
- The inspector bundle polls its configured local UI endpoint and clears its timer when the component is removed.
- Remote resolution clones or refreshes the repository specified by the caller.
- Inspector run execution starts npx kraftwerk run with the chosen workflow and request.
- Chat skills expand only after a message explicitly starts with a matching skill command.
- Docker runs mount the selected workflow read-only and bind the run output directory.
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.10.2.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.10.2 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.