This document discusses the risks of using mobile SDKs in apps. It notes that apps on average contain 57-60 SDKs from third parties, adding significant code that developers are responsible for but did not write. SDKs can pose security, privacy, and quality risks if they access sensitive permissions or system resources without the user's knowledge. The document provides examples of SDKs automatically granting themselves permissions or loading code in the background. It recommends that developers carefully audit the SDKs used in their apps and remove unused permissions to reduce security and privacy risks for users.