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.
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.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?