@netnodeag/kraftwerk@0.19.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-aiThe package has no automatic registry-install lifecycle hook or self-dependency, and the inspected behavior is activated through explicit product actions. Because it orchestrates arbitrary workflows and can forward credentials, it warrants a warning rather than a clean verdict despite no concrete malicious chain.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user starts a workflow, invokes the inspector, selects a remote workflow, or enables sandbox and SSH options.
Impact
A malicious workflow supplied by the user or a remote source could execute commands with the permissions and credentials deliberately provided to it.
Mechanism
User-configured workflow execution with optional Docker credential forwarding.
AI rationale
The package has no automatic registry-install lifecycle hook or self-dependency, and the inspected behavior is activated through explicit product actions. Because it orchestrates arbitrary workflows and can forward credentials, it warrants a warning rather than a clean verdict despite no concrete malicious chain.
Evidence
dist/remote.jsdist/inspector/runner.jsdist/runner/docker.jsdist/inspector/chat/sessions.jsdist/run.js
Network endpoints1
github.com/
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package exposes a command-line workflow framework; its only lifecycle hook is prepublish, not an install hook.
- The inspector can start a detached `npx kraftwerk run --yes` process in the consumer project.
- Remote workflow specifications clone, fetch, and hard-reset Git repositories under a user cache.
- Sandboxed runs pass configured environment files, API-key variables, and optionally an SSH agent socket into Docker.
- Chat messages can expand local SKILL.md content into agent instructions.
- Configured workflow script phases execute Bash with the inherited environment.
Evidence against
- No preinstall, install, or postinstall lifecycle script is declared.
- No self-dependency is declared in package.json.
- The risky operations are reachable through explicit CLI, UI, workflow, or sandbox actions rather than package installation.
- No source evidence shows secret collection followed by exfiltration, stealth persistence, or destructive behavior.
Behavioral surface
ChildProcessCrypto
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.19.0.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.19.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.