kveton ↗ analysis ↗ GitHub kveton/mike
A security-focused Mike fork proposal centered on keeping sensitive legal-work data under tighter server control.
kveton's fork outlines a broad security hardening pass for Mike, aimed at making sensitive data handling more deliberate across access, credentials, and document uploads.
The proposed direction puts the browser in a less trusted role: sensitive data access would be mediated by the backend, LLM API keys protected at rest, and uploaded documents checked before storage. It is a practical security-and-infrastructure story rather than a new legal-workflow product.
There are no tracked changes ahead of Mike, and the described proposal was closed without merging. Click through to GitHub for the underlying discussion and detail.
What's in it
- Backend-mediated access Moves sensitive application data access behind server-side controls.
- Protected LLM credentials Proposes encryption for user-supplied LLM API keys stored by the service.
- Safer document uploads Adds validation of uploaded document contents before they are stored.
- Tighter sharing controls Strengthens authorization around documents, project scope, and direct-share edits.
Direction
securityinfrastructure
Activity
Threads of work (detailed view)
kveton proposes backend-mediated auth and LLM key encryption across the full stack
kveton/mike describes a security hardening PR that moves sensitive Supabase table access behind backend service-role APIs, encrypts LLM API keys at rest, validates uploaded file bytes before storage, and tightens authorization across document access, project scoping, and direct-share edits. The PR was closed without merging on 2026-05-10.
Pull requests (detailed view)
⛔ Closed without merge (1)
kveton · opened 6mo ago · closed 6mo ago