@netnodeag/kraftwerk@0.20.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 2mo ago · by lpm-firewall-aiNo concrete malicious install hook, exfiltration path, or persistence behavior was found. The unscoped runtime npx invocation is nevertheless a credible dependency-confusion vulnerability.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user starts a workflow from the inspector UI.
Impact
An unrelated registry package could be installed and executed in the consumer project context.
Mechanism
Detached unscoped npx execution of a workflow command.
AI rationale
No concrete malicious install hook, exfiltration path, or persistence behavior was found. The unscoped runtime npx invocation is nevertheless a credible dependency-confusion vulnerability.
Evidence
dist/inspector/runner.jsoutput/runs/<id>/trigger.log
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Critical Vulnerability with low false-positive risk.
Evidence for warning
- The inspector's run trigger starts `npx kraftwerk`, an unscoped and unpinned package command; if no local binary is resolved, this can fetch an unrelated registry package.
- User-selected workflow script phases execute supplied Bash text in the run directory.
- The `--from` feature clones a user-supplied Git remote into a cache.
- Sandbox runs intentionally pass configured API-key environment variables into the workflow container.
- The manifest has no install, preinstall, or postinstall lifecycle hook.
Evidence against
- The observed risky actions are reached through explicit CLI or inspector workflow actions, not package installation or import.
- No source evidence shows credential collection followed by network exfiltration.
- No self-dependency or automatic nested installation chain is declared.
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.20.0.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.20.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.