registry / @netnodeag/kraftwerk / 0.17.1
@netnodeag/kraftwerk@0.17.1
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 high-risk primitives are consistent with an explicitly invoked workflow-orchestration CLI and have no install-time trigger. Static inspection found no concrete malicious behavior or self-dependency chain.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user starts a workflow, uses the inspector, selects Docker sandboxing, or supplies a remote workflow source.
Impact
User-selected workflows may run local AI agents with the permissions and environment the user provides; no covert package-originated exfiltration or persistence was found.
Mechanism
User-invoked workflow orchestration through local CLIs, Docker, and git.
AI rationale
The high-risk primitives are consistent with an explicitly invoked workflow-orchestration CLI and have no install-time trigger. Static inspection found no concrete malicious behavior or self-dependency chain.
Evidence
.cache/kraftwerk/remotes<project>/output/runs/<runId><project>/runner.env
Network endpoints2
registry.npmjs.org/${name}/latestgithub.com/${orgRepo}.git
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package provides a workflow runner that can invoke local AI-agent CLIs with workspace-write access.
- Its inspector can start a detached npx workflow run in the selected project.
- Optional Docker mode passes declared API-key environment variables into a container and can mount an SSH agent when explicitly requested.
- Remote workflow sources are cloned or refreshed with git into a user cache.
Evidence against
- package.json has only a prepublishOnly hook, so registry installation has no automatic lifecycle execution.
- The npx and Docker actions are reached through runtime CLI or inspector workflow triggers, not import or install.
- No credential harvesting, secret exfiltration, hidden downloader, eval, or reviewer-directed text was found in the inspected source.
- The npm-registry request is a bounded version check in the explicit doctor command.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
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.17.1.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.17.1 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.