b1rdmania/mike

A legal-workspace fork exploring verifiable document exports and safer contributor setup.

Despite 17 tracked threads, the fork currently shows no commits ahead of Mike and no push since 2026-08-02, so it appears paused or still in an exploratory stage.

View on GitHub →

b1rdmania is shaping Mike around a practical trust question: can a recipient verify that an exported document is the version the workspace held? The clearest direction is tamper-evident project exports, using per-version fingerprints to support independent checking.

The fork also gives attention to the contributor experience: safer local testing with disposable services and synthetic documents, clearer handling of public versus secret settings, and focused contribution guidance. It is a small, security-minded product direction rather than a visible rebrand or new legal-practice niche.

What's in it

Direction

securityinfrastructureworkflow

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.

📝 Simplify JSON body parsing 3 commits 3mo ago minor change
✅ #273 Remove dead jsonLimitForPath abstraction +5 -7 3mo ago by b1rdmania ↗ analysis ↗ GitHub
`jsonLimitForPath()` ignores its `path` argument and always returns `"50mb"`, and the per-request wrapper re-invokes `express.json()` on every request for no effect. This replaces both with a single static `express.json(…
📝 Surface safe local testing guidance and split frontend env vars 0 commits — minor change
📝 Add a contributor guide for the Mike fork 0 commits — minor change

Threads of work (detailed view)

2 threads have been distilled into posts.

Pull requests (detailed view)

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

✅ Merged (2)

⛔ Closed without merge (3)