other
- Location
dist/mcp/server.js:3052- Finding
Repository Source Code Is Transmitted to Remote Embedding Services
- Content
View full analysis
t.length > maxChars ? t.slice(0, maxChars) : t); const response = await fetch(`${apiBase}/embeddings`, { method: "POST", headers: { "Content-Type": "application/json", Authorization: `Bearer ${apiKey}` }, body: JSON.stringify({ model, input: truncatedTexts }) }); ``` ### Technical Analysis The `nella_index` operation reads repository files, divides their contents into text chunks, and passes those chunks to an embedding provider. When the Nella provider is selected, the `texts` array is serialized into the HTTP request body and sent to `https://app.getnella.dev/api/embeddings`. The same embedding implementation also supports Voyage and Azure providers. Consequently, indexing is not necessarily a local-only operation: substantial portions of repository source code can leave the user's environment. Although `.gitignore` and `.nellaignore` patterns are supported, these controls do not guarantee that sensitive tracked files are excluded. API credentials, private keys embedded in source files, proprietary algorithms, customer information, configuration values, and regulated data can still be transmitted. The reviewed `SKILL.md` and README describe indexing and code search but do not clearly state that source-code chunks may be uploaded to an external embedding service. ### Attack Path 1. A user installs and configures the Nella MCP server for a private repository. ...[truncated 1016 chars]- Remediation
View remediation
