{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Go: Can It Mitigate Supply Chain Attacks?","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/fee8cb04\"></iframe>","width":"100%","height":180,"duration":482,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/go-can-it-mitigate-supply-chain-attacks.\nIt is an explicit security design goal of the Go toolchain that neither fetching nor building code will let that code execute, even if it is untrusted.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #go, #golang, #supply-chain, #supply-chain-attacks, #version-control-system, #go-for-beginners, #go-guide, #golang-safety,  and more.\nThis story was written by: @Go. Learn more about this writer by checking @Go's about page,\n            and for more stories, please visit hackernoon.com.\nAll together this means it’s possible to build rich, complex applications with just a handful of dependencies. No matter how good the tooling is, it can’t eliminate the risk involved in reusing code, so the strongest mitigation will always be a small dependency tree.","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}