registry / @netnodeag/kraftwerk / 0.44.0
@netnodeag/kraftwerk@0.44.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-aiThe package contains powerful but product-aligned, user-invoked orchestration features and no automatic install hook or confirmed covert payload. The minified editor asset's invisible character does not establish malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user starts a workflow, enables a configured preview, or requests a remote workflow.
Impact
Configured commands and workflows can act with the permissions granted by the user.
Mechanism
User-directed workflow, agent, Docker, and preview orchestration.
AI rationale
The package contains powerful but product-aligned, user-invoked orchestration features and no automatic install hook or confirmed covert payload. The minified editor asset's invisible character does not establish malicious behavior.
Network endpoints2
github.com/registry.npmjs.org/
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no install lifecycle hook; its only publish hook builds release artifacts.
- The inspector can start a workflow through npx only after a UI run request.
- A configured vibeable development command is deliberately run through a shell after its project configuration is selected.
- Remote cloning occurs only for an explicit --from source and validates github shorthand.
- Agent definitions are stored in the consumer project and use constrained slug validation.
- The reported invisible character is in a minified browser editor asset; no hidden execution path was established.
Evidence against
- No preinstall, install, or postinstall behavior was found.
- No credential harvesting or secret exfiltration was found.
- Network use is limited to an explicit remote clone and an inspector update check.
- Process execution implements the package's user-invoked workflow, agent, Docker, and preview features.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVars
Source & flagged code
8 flaggeddist/remote.jsView file
1import { spawnSync } from "node:child_process";
L2: import { mkdir, stat } from "node:fs/promises";
High
dist/inspector/vibeables.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @netnodeag/kraftwerk@0.2.0
matchedIdentity = npm:QG5ldG5vZGVhZy9rcmFmdHdlcms:0.2.0
similarity = 0.458
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/inspector/vibeables.jsView on unpkg546cwd: r.dir,
L547: shell: true,
L548: detached: process.platform !== "win32",
High
Findings
2 Critical4 High4 Medium6 Low
CriticalTrojan Source Unicodeinspector/dist/assets/editor-D__mCVTd.js
CriticalPrevious Version Dangerous Deltadist/inspector/vibeables.js
HighChild Processdist/remote.js
HighShelldist/inspector/vibeables.js
HighRuntime Package Installdist/inspector/runner.js
HighSemantic Analysis Limiteddist/inspector/agents.js
MediumDynamic Requirebin/kraftwerk.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptodist/inspector/instances.js
Affected versions and remediation
This report applies to @netnodeag/kraftwerk@0.44.0.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.44.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.