What decides whether Magpie survives a real build is verification. Gradle resolves hundreds of artifacts transitively, so fixing one rate limit just spreads your trust across whoever runs the Blossom servers. Carry the sha256 of every artifact inside the release event and check the blob against it on fetch. A compromised server can then serve garbage, but it cannot serve different bytes under the same name.

Replies (1)

↑