@netnodeag/kraftwerk@0.46.2
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-aiNo malicious install hook, credential theft, exfiltration, or covert persistence was found. The package nevertheless provides explicit agent-control mutation and shell execution through its inspector, so it warrants a warning rather than a clean verdict.
Decision evidence
public snapshot- The inspector exposes a POST route that starts a project-defined development command.
- That command is run through a shell with the full inherited environment.
- The inspector API writes agent configuration and system-prompt files in the selected project.
- The package can clone or refresh a user-supplied remote Git repository into its cache.
- The manifest has no automatic install lifecycle hook; its only publish hook is prepublishOnly.
- The shell execution is reached through an explicit inspector API action and uses the selected vibeable directory.
- Agent files are constrained to validated slugs beneath the configured project agents directory.
- No source inspected showed credential harvesting, secret exfiltration, stealth persistence, or an install-time payload.
- The inspector defaults to loopback binding outside containers.
Source & flagged code
8 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/inspector/vibeables.jsView on unpkgFindings
Affected versions and remediation
This report applies to @netnodeag/kraftwerk@0.46.2.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.46.2 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.