BradyOnTech quietly deletes Mike's license

The fork's single change strips out the open-source license that legally governs the code - but the obligations don't go with it.

compliance

BradyOnTech's only change to its copy of Mike removes the project's license entirely: the license file is gone, and the metadata that used to name it now sits blank. No code was touched. The commit message says only "new main."

Here's why that matters. Mike is published under AGPL-3.0, a "copyleft" license that forces anyone who runs a modified version as a service to publish their source code. A downstream fork can't cancel that by deleting a file - the original author's terms still apply no matter what the fork's labels say. So a blank license field doesn't make the code free to use; it just hides the strings that are still attached. Anyone evaluating this fork should treat it as AGPL-bound regardless of how it presents itself.

So what If your team is sizing up legal-AI code to build on, this is a reminder to check the upstream license yourself - the fork's own labels can be wrong, and AGPL obligations follow the code.

View this fork on GitHub →

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

Commits in this thread

1 commit from BradyOnTech/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
7fb43d8b new main bradyontech 2026-04-30 ↗ GitHub

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-142.md from inside the repo you want the changes in.

⬇ Download capture-thread-142.md