Malus, which is a piece of “satire” but also fully functional, performs a “clean room” clone of open source software, meaning users could then sell, redistribute, etc. the software without crediting the original developers. But I have a hard time with the “clean room” argument since the LLM doing the behind-the-scenes work has already ingested the entire corpus of open source software – and somehow the output of the LLMs isn’t considered a derivative work.
If you’re referring to GPL variants, that depends. You can absolutely use GPL software and libraries with closed source software. You just need to separate the GPL portions from the closed source portions with some sort of boundary, like running it as a service of some sort or turning it into a CLI tool. You’re just not allowed to create derivative works of GPL software that isn’t also GPL.
Also, there should be nothing dangerous about open sourcing code (unless you’re referring to financial risk to the business I guess). Secrets should never live in code, and obscurity is never secure.
Pretty sure that e.g. manufacturing techniques for physics based design are highly problematic. So is the software for military communications. The real world is in fact real.
Your first example isn’t even code, and in your second if the “software” was remotely well architectured its configuration (not code) is what would need to be kept secret. You’re also very rude!