registry / @netnodeag/kraftwerk / 0.23.0
@netnodeag/kraftwerk@0.23.0
Open-source agentic workspace for teams — where people and AI agents get work done together: agents (Claude Code, Codex, Pi), skills, shared knowledge, repeatable workflows, and deterministic verification
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is an agentic workflow CLI with powerful but user-invoked command execution and sandbox features. It has no registry install hook, self-dependency chain, stealth persistence, or confirmed exfiltration behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs a workflow, starts the inspector, selects a remote source, or enables sandbox SSH forwarding.
Impact
User-authored or user-selected workflows can run commands with the permissions the user grants.
Mechanism
User-directed workflow orchestration and optional Docker execution.
AI rationale
This is an agentic workflow CLI with powerful but user-invoked command execution and sandbox features. It has no registry install hook, self-dependency chain, stealth persistence, or confirmed exfiltration behavior.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- User-selected workflows can execute Bash scripts.
- The optional Docker runner forwards selected API keys and SSH access only when requested.
- Remote workflow sources are cloned into a local cache.
- The inspector can launch a user-requested workflow through npx.
- The chat module describes workflow execution as a user-directed action.
- The manifest has only a publish-time build hook, not an install lifecycle hook.
Evidence against
- No preinstall, install, or postinstall script is present.
- No secret collection or outbound exfiltration code was found.
- No runtime dependency on this package itself is declared.
- Risky execution features are explicit CLI, workflow, UI, or sandbox functions.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinified
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.23.0.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.23.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.