kveton/mike

A security-focused Mike fork proposal centered on keeping sensitive legal-work data under tighter server control.

This appears paused: it was first seen and last updated on 2026-05-07, with no tracked changes ahead of Mike.

View on GitHub →

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

Direction

securityinfrastructure

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

Threads of work (detailed view)

1 thread have been distilled into posts.

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)

1 PR touch this fork — inbound (filed against it) or outbound (filed from it). State icons match the editorial dashboard.

⛔ Closed without merge (1)