BradyOnTech quietly strips the license off Mike

The fork's only commit deletes the AGPL license file and blanks the license field in the project metadata, with no code changes attached.

complianceinfrastructure

Mike ships under AGPL-3.0, a copyleft license that lets anyone use and modify the code but requires downstream forks to keep the same terms and share their changes. BradyOnTech's fork is a single commit that removes the license file entirely, drops the license section from the README, and empties the license field in the project's package metadata. The commit message is just "new main."

A downstream fork can't unilaterally relicense AGPL code, so the metadata is misleading rather than legally effective. But the intent it signals is the interesting part: someone appears to be preparing to present Mike as if it were unencumbered. Any code changes that show up in this fork later are still bound by AGPL, regardless of what the repo claims about itself.

So what If you're evaluating Mike forks for your own legal-tech stack, this is one to watch but not borrow from - pulling code from it would inherit the compliance question, not escape it.

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