Issue #234 — Auditing Swift Package Dependencies & Privacy Manifests
Modern iOS apps ship with dozens of transitive packages. Since Apple introduced mandatory PrivacyInfo.xcprivacy manifests for commonly used SDKs and Required Reason APIs, auditing every dependency in your Package.resolved or Podfile.lock is essential before submitting an update.
High-Risk Required Reason APIs to Audit
| API Category | Common Call Site | Required Reason Code |
|---|---|---|
| UserDefaults | UserDefaults.standard | CA92.1 (App-only preferences) |
| File Timestamp | URLResourceValues.contentModificationDate | C617.1 (App container files) |
| System Boot Time | ProcessInfo.systemUptime | 35F9.1 (Elapsed time measurement) |
| Disk Space | volumeAvailableCapacityKey | E174.1 (Checking space before write) |
Lightweight Release Notes Without Bloat
Libraries like WhatsNewKit remain popular among indie developers because they present version-gated changelog sheets cleanly without pulling in heavy analytics SDKs. Before adding any UI dependency, verify its license, minimum iOS deployment target, and whether it bundles a signed privacy manifest (documented in Apple Privacy Manifest Files).