Evaluate a Third-Party SDK (Build vs Buy)

Background: Native [platform] app. I'm considering adding this
dependency: [SDK/library name and what it does]. The alternative is
building it myself in roughly [estimate] of work.

Use case: Help me decide whether to add this SDK or build the capability
in-house, and if I add it, how to vet it first.

Implementation details: Evaluate against:
- Binary size added and effect on app startup
- Permissions / privacy data it collects (App Store privacy nutrition
  label / Play Data safety implications)
- Maintenance health (release cadence, open issues, last commit, license)
- Whether it pulls in transitive dependencies or its own networking
- How hard it is to remove later if it goes unmaintained
- iOS: SwiftPM vs CocoaPods support; Android: AAR size, min SDK

Layer & dependencies: If adopted, it must be wrapped behind my own
interface so the app codebase doesn't import it everywhere.

Deliverable: A build-vs-buy recommendation with reasoning, a vetting
checklist result for this specific SDK, the risks of adopting it, and a
wrapper-interface sketch that isolates it.