@vibekiln/cutline-mcp-cli-staging@0.8.1
CLI and MCP servers for Cutline, including SlopBurn: a product quality engineering roguelike RPG for vibecoding workflows.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package’s explicit `init` flow sends authenticated installation and usage telemetry to the publisher’s service, including stable project-derived identifiers, with no disclosure or opt-out found in the inspected materials. This is a warning-level telemetry concern; no malicious credential redirection or install-time behavior was confirmed.
Decision evidence
public snapshot- The explicit `init` command sends an authenticated install registration and follow-up usage events without a documented telemetry opt-out found in the inspected package materials.
- Registration derives stable installation and workspace identifiers from the project path and sends them to the Cutline service.
- The event payload records command and setup details, including tier and generated rule count.
- Telemetry is triggered by the user running `init`, rather than by an install hook or package import.
- The registration and event requests target the package’s own Cutline service; the project path is hashed before sending.
- The manifest’s only lifecycle script is `prepublishOnly`, which runs a build rather than install-time code.
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.1.
See all versions of @vibekiln/cutline-mcp-cli-staging for other recorded verdicts.
- Review the evidence and your use of @vibekiln/cutline-mcp-cli-staging@0.8.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.