we put it in the repo README, will add migrate more into public repo as soon as possible.

It has to be 100% open source public code or we will have no way of proving this is not malware, or secretly swapped out for malware later when your CI/CD system or laptop is compromised. Supply chain attacks happen all the time and with closed code no one will be equipped to spot it when it happens.

Also, security aside, engineers want the freedom to modify and experiment with the tools we rely on.

Tools like this are too important to be closed. Do you want to be Internet Explorer or Firefox?

▲

ubermon 38 minutes ago | parent [-]

Oh no, definitely not Internet Explorer. Will figure out a way to ship with source first to address the security and concern and then figure out how to do the open source development in agentic era later, I was too carried away by the complexity of the latter and ignorant to the former.

	▲	lrvick 28 minutes ago \| parent [-]
		When it is 100% freely licensed open source software I can modify and compile myself, I will be happy to give it a shot.