registry / @netnodeag/kraftwerk / 0.46.1
@netnodeag/kraftwerk@0.46.1
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 high-risk primitives are product-aligned, user-triggered automation features, while the published package has no install lifecycle hook or self-dependency. No credential exfiltration, covert persistence, or automatic foreign control-surface mutation was found.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user starts a workflow, preview development server, remote workspace, or update action.
Impact
Configured workflows or preview commands can run with the invoking user's permissions, as expected for this automation tool.
Mechanism
User-directed local process launching and workspace configuration management.
AI rationale
The high-risk primitives are product-aligned, user-triggered automation features, while the published package has no install lifecycle hook or self-dependency. No credential exfiltration, covert persistence, or automatic foreign control-surface mutation was found.
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 contains user-invoked command execution for workspace workflows, preview development servers, and remote repository handling.
- The bundled editor asset contains invisible Unicode characters, but source inspection found it to be a minified frontend asset rather than an install-time payload.
Evidence against
- The manifest has only a prepublishOnly hook; installation does not run a lifecycle script.
- There is no dependency on this package's own name and no automatic nested lifecycle chain.
- Command execution is reached from explicit CLI or local UI actions and uses workspace configuration or user-selected workflows.
- The inspector binds to loopback by default and its source explicitly limits Git staging of environment and credential files.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
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-DJbeG376.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.46.1.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.46.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.