What problem does it solve? Push notification misuse — requesting permission at launch, sending marketing content without opt-in, or carrying ads — is a common cause of App Store rejection under Guideline 4.5.4, and these issues are easy to miss in code review. ## Core Features & Use Cases - Launch-Time Permission Detection: Finds UNUserNotificationCenter.requestAuthorization calls inside application(_:didFinishLaunchingWithOptions:) or scene(_:willConnectTo:). - Marketing and Ad Content Scanning: Greps notification payload strings for promotional keywords like "sale", "discount", and "sponsored" near UNMutableNotificationContent. - Delegate and Entitlement Checks: Verifies UNUserNotificationCenterDelegate is implemented and that aps-environment exists in the app's entitlements file. - Use Case: Before submitting an iOS app for review, run this audit to get a prioritized findings list (CRITICAL/HIGH/MEDIUM/LOW) with file paths, line numbers, and fixes for each push notification violation. ## Quick Start Audit my iOS project for push notification violations of App Store Guideline 4.5.4 and list the findings with file locations.