@netnodeag/kraftwerk@0.45.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-aiNo malicious install lifecycle or exfiltration was found, but the unscoped npx launcher creates a concrete unresolved dependency-confusion execution path. This warrants a warning until it invokes the scoped package or its own resolved executable.
Decision evidence
public snapshot- The inspector launches `npx kraftwerk run` without the package scope from the consumer project.
- A UI POST request reaches that launcher, so an absent local binary can cause npx to resolve and execute an unrelated registry package.
- This differs from the package's own fallback, which correctly uses `@netnodeag/kraftwerk`.
- package.json has no preinstall, install, or postinstall hook; its only lifecycle script is prepublishOnly.
- No credential harvesting, secret exfiltration, or covert network request was found in the inspected execution paths.
- Most process execution is part of explicit workflow, Docker, agent-harness, or UI actions.
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.45.1.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.45.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.