I understand you are trying to push a more secure set of standard operating procedures. And as far as that goes I would agree. But to take it further and simply declare the method itself as inherently bad just because it can be abused by adversarial control that I would probably not agree with. Every instance you show of this being an issue relies on something being provided by a malicious actor - whether thats typosquatting (IE- wrong address, incorrect execution) or the supplier of the scri...