@vibekiln/cutline-mcp-cli-staging
CLI and MCP servers for Cutline, including SlopBurn: a product quality engineering roguelike RPG for vibecoding workflows.
This report shows the evidence for @vibekiln/cutline-mcp-cli-staging@0.8.2. 0 of 4 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has no confirmed credential exfiltration or install-time attack, but its opt-in HTTP bridge has no authentication and binds to all interfaces by default. That exposes local MCP operations, including a shell-based test execution path, to any caller who can reach the port.
Decision evidence
public snapshot- When HTTP bridge mode is enabled, it binds to 0.0.0.0:8080 by default and forwards JSON-RPC requests to the MCP server without an authentication check.
- The SlopBurn verification action enables generated-test execution by default, and its helper runs a shell command with the full process environment.
- The bridge requires the explicit --http option; no install-time or import-time attack behavior was identified.
- The inspected credential flow sends refresh tokens to Google Secure Token and Cutline ID tokens to Cutline endpoints.
- HTTP bridge mode is explicitly opt-in through the serve command’s --http option.
- The shell execution is part of SlopBurn’s local test-verification workflow and uses its configured test command.
Source & flagged code
8 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/commands/serve.jsView on unpkgPackage source references child process execution.
dist/commands/serve.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @vibekiln/cutline-mcp-cli-staging@0.8.2.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @vibekiln/cutline-mcp-cli-staging@0.8.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.