jsw324 is quietly shipping Mike as 'unburdn law'

A routine security upgrade comes bundled with a product rebrand that points to a real go-to-market.

brandinginfrastructure

Two commits do double duty. The first patches four security vulnerabilities flagged by Railway (the cloud host this fork deploys on) and, in the same breath, swaps every user-visible mention of 'Mike' for a lowercase 'unburdn law' - page titles, sidebar, the AI assistant's self-introduction, the author name stamped on tracked-changes in Word exports, and the signup page's terms and privacy links, which now point to unburdn.ai. The second commit cleans up a lockfile snag so Railway can build a fresh copy without manual fiddling.

What's telling is what jsw324 left alone: internal code names, package identifiers, the file-format plumbing. This is skin-deep on purpose. Someone is putting a brand on the storefront while keeping the engine recognisably Mike underneath - the move of a builder readying a commercial offering, not a researcher tinkering in public.

So what Worth watching for anyone tracking which Mike forks are heading toward paying customers versus staying experimental.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from jsw324/law-llm, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`492dd408`	Bump Next.js to ^16.0.11 and rebrand to unburdn law	Jason Walkow	2026-05-03	↗ GitHub
commit body Fixes critical CVEs in next@16.0.3 (CVE-2025-66478, CVE-2025-55184, CVE-2025-67779, CVE-2025-55183) flagged by Railway's security scan. Also resolves the @opennextjs/cloudflare peer-dep conflict that blocked fresh installs. Replaces user-visible "Mike" branding with lowercase "unburdn law" across page titles, sidebar/logo, AI persona system prompts, DOCX tracked-changes author, signup terms/privacy URLs, and column-prompt placeholders. Internal type names, MIME types, package names, and the MikeIcon component are unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
`99375788`	Remove frontend/bun.lock so Railpack uses npm + package-lock.json	Jason Walkow	2026-05-03	↗ GitHub
commit body Railpack prefers bun when bun.lock is present, but the file was stale relative to package.json after the Next.js bump and failed --frozen-lockfile. The repo standardizes on npm per the README, so the bun lockfile is unused - removing it lets Railpack fall back to npm and the up-to-date package-lock.json. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-104.md from inside the repo you want the changes in.

⬇ Download capture-thread-104.md