BradyOnTech/mike

Fork with one commit: AGPL-3.0 license removed, no code changes

Inactive from an engineering standpoint. One commit, no code changes, license-removal only. The fork shows no sign of development work beyond the initial fork action.

View on GitHub →

BradyOnTech/mike has a single commit ahead of upstream. It deletes the LICENSE file, removes the license section from README.md, and blanks the "license" field in both package.json files. No code modifications accompany this.

The upstream codebase is AGPL-3.0-only. Removing the license markers does not change the legal status of the code - the terms still apply. This is a compliance concern rather than a technical one, and there are no engineering contributions to evaluate.

Direction

branding

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

📝 BradyOnTech quietly deletes Mike's license 1 commit 3mo ago compliance draft

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

Threads of work (detailed view)

2 threads have been distilled into posts.

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

1 commit · latest 3mo ago

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.

complianceinfrastructure

1 commit · latest 3mo ago