Most compilers that produce native, static binaries for a platform also use static type systems that can be used to determine exactly where and how any given pi

Most compilers that produce native, static binaries for a platform also use static type systems that can be used to determine exactly where and how any given piece of code is used, including libraries. Also, if one can't get their internal builds correct, then they've got problems that go beyond security concerns. Also, if you're talking about native, highly-distributed desktop/server applications, then the problem with using shared libraries is even worse. The only exception is system-level libraries that are updated automatically by the OS/distribution. Finally, on Windows, with static binaries you can be sure that the binary is a particular version/build and is signed (this ensures that the binary version/build is valid). You don't get much better peace of mind than that. We've been distributing our installations and other binaries like that for over a decade, and it works great.