Fork's first commit deletes the AGPL-3.0 license
BradyOnTech's only change to the codebase is removing the license. The `LICENSE` file is gone, the README license section is gone, and both `package.json` files now have empty `"license"` fields. No code changes accompany this.
Commit 7fb43d8 ("new main") deletes all 661 lines of the AGPL-3.0 LICENSE file, drops the ## License section from README.md, and sets "license": "" in both backend/package.json and frontend/package.json.
This is a compliance red flag. Upstream willchen96/mike is AGPL-3.0-only, which is copyleft. A downstream fork cannot unilaterally strip or override the upstream license - those terms continue to apply to the code regardless of what the fork's metadata says. Presenting the project with blank license fields misrepresents its status to anyone who encounters the fork without knowing its upstream.
The vague commit message gives no explanation for the removal. Any future commits from this fork carry the same compliance risk: the code remains AGPL-3.0 bound even if the fork author has removed the markers saying so.
The only arguably separable change is removing the license blurb from the README, but it's bundled with the LICENSE deletion and package.json edits.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?