Hacker News Reader

> With those modifications, it then builds Python from source across a wide matrix of Python versions, platforms, and build variants (e.g., optimized vs. debug builds), and publishes the built distributions to GitHub Releases.

This should be illegal.

View on HN

How to handle this situation is literally defined in the LICENSE for any modern software project

Why?

Supply chain risk.

Please explain your reasoning.

Somebody else is building your binaries. You've added another link in your software supply chain. How do you know they haven't inserted malware?

> Somebody else is building your binaries.

That happens all the time. Who builds the docker images you are using?

> You've added another link in your software supply chain. How do you know they haven't inserted malware?

You're installing untrusted random packages from PyPI. There are many much weaker points than Astral giving you malware for fun.

Sure it happens, but that doesn't mean you shouldn't think about reducing it.

> Somebody else is building your binaries.

FYI there are two parties you are talking about: Astral, and GitHub too (if you don't trust Microsoft).

Publishing to Github should be considered a crime.

Reply on news.ycombinator.com