Metbcy/mike

This is Metbcy's fork of Mike, and right now it sits essentially in step with upstream - no divergence to speak of. If you cloned it today you'd get the Mike you already know, plus one focused piece of security hardening.

That piece is worth the click: @Metbcy closed a signature-forgery gap in the download subsystem. Signed download links are protected by a keyed HMAC, but the backend used to fall back to a hardcoded placeholder secret when no real one was configured - which quietly opened the door to forged tokens. The fork makes the backend refuse to start without a real secret, so a misconfigured deployment fails loudly instead of trusting bad links.

Beyond that single thread, there's little to read into here. No rebrand, no stated niche, no product direction being telegraphed - just a security-minded fix from someone paying attention to how downloads get authenticated. Click through to GitHub if you want the specifics.