registry / slashvibe-mcp / 0.8.22
slashvibe-mcp@0.8.22
Presence + messaging for terminal coding agents (Claude Code, Codex, Cursor) — the /vibe kernel
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe routed findings are explained by ordinary handle normalization and package features. The reviewed credential requests go to the package's own service, while setup and tipping are user-triggered; no malicious behavior was found.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
MCP startup, explicit onboarding or setup commands, or a user-requested message with a positive tip amount.
Impact
No unauthorized credential transfer, account action, or other malicious impact was identified in the reviewed paths.
Mechanism
The reviewed requests use the package service; profile lookup sends its saved token there, and onboarding sends repository name and tech stack for a personalized welcome.
AI rationale
The routed findings are explained by ordinary handle normalization and package features. The reviewed credential requests go to the package's own service, while setup and tipping are user-triggered; no malicious behavior was found.
Network endpoints1
www.slashvibe.dev
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes its MCP server and setup wizard as entry points and declares no install lifecycle script.
- The zero-width and bidi characters in protocol/handle.js are explicitly removed to normalize handles.
- During onboarding, init sends the detected repository name and tech stack to slashvibe.dev for a personalized welcome.
- Profile lookup sends the saved token to the package service's profile endpoint.
- The CLI invokes setup when the user supplies the setup command.
- A tip is sent only when a positive tip amount is supplied and a saved token is available.
Evidence against
- Setup writes configuration as part of the explicitly invoked setup flow.
- The inspected credential-bearing requests target the package's own slashvibe.dev service.
- No malicious behavior was identified in the reviewed startup, onboarding, handle-normalization, or messaging paths.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
6 flaggedtools/_work-context.jsView file
12L13: const { execFileSync } = require('child_process');
L14: const fs = require('fs');
High
Child Process
Package source references child process execution.
tools/_work-context.jsView on unpkg · L12tools/init.jsView file
11L12: const { exec, execSync } = require('child_process');
L13: const fs = require('fs');
...
L21:
L22: const API_BASE = 'https://www.slashvibe.dev';
L23:
...
L25: // "vibe email …" advertises a command their session does not have.
L26: const EXTRAS_ENABLED = ['1', 'true'].includes(String(process.env.VIBE_EXTRAS || '').toLowerCase());
L27:
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
tools/init.jsView on unpkg · L11protocol/handle.jsView file
Findings
3 Critical4 High3 Medium4 Low
CriticalTrojan Source Unicodeprotocol/handle.js
CriticalTrigger Reachable Dangerous Capabilityprotocol/handle.js
CriticalPrevious Version Dangerous Deltasetup.js
HighChild Processtools/_work-context.js
HighShell
HighSame File Env Network Executiontools/init.js
HighSemantic Analysis Limitedindex.js#virtual:string-array:round1
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to slashvibe-mcp@0.8.22.
See all versions of slashvibe-mcp for other recorded verdicts.
- Review the evidence and your use of slashvibe-mcp@0.8.22 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.