Store bundle static scan, dormant code and Local Network prompt triggers
Parent: Apple Platform Publishing (Mac App Store) · Topic entry · 17 branches · skill apple-platform-publishing/references/store-bundle-static-scan-dormant-code-local-network-prompt.md
A published reference is not available for this topic yet.
Children
- Staged-source build: run py2app on a pruned copy of the package instead of deleting afterwards (frontier)
- Clean-venv reproducible py2app build and a "no unexpected distributions" gate (mcp contamination) (frontier)
- What runs at upload (altool/Transporter validation) versus at review (string and symbol scans): a timeline per guideline (frontier)
- Observing Local Network decisions: nehelper and mDNSResponder log predicates, fresh-account and VM procedures (frontier)
- Responsible-process attribution for setuid children (/sbin/ping) under App Sandbox and Local Network privacy (frontier)
- ICMP and Local Network privacy: does ICMP echo to an on-link host count? (frontier)
- com.apple.network.local-network allow-list defaults (AllowedWiFiLocalNetworkAddresses) for review-network testing (frontier)
- network.server justification patterns when the listener is user-enabled (2.4.5(i) precedents) (frontier)
- Purpose-string review under 5.1.1(ii): wording for conditional features (frontier)
- Splitting privileges.py into constants and actions so the actions can be omitted (Tier 2) (frontier)
- Splitting failover.py into read-only listing and write path (Tier 3) (frontier)
- py2app recipes that force packages in (detect_dunder_file) and how to override them (frontier)
- Source versus bytecode versus zip for first-party code: visibility to reviewers and scanners (frontier)
- Notes for Review dormant-feature disclosure patterns and a template library (frontier)
- Info.plist hygiene for py2app builds (PythonInfoDict developer path, NSAppleScriptEnabled) (frontier)
- Executable data files inside stdlib packages (fetch_macholib) and bundle-wide executable audit (frontier)
- Interaction of the Local Network prompt with the screen-recording demo script (timer fire date, restart-only settings) (frontier)
Frontier under this node: Clean-venv reproducible py2app build and a "no unexpected distributions" gate (mcp contamination), Executable data files inside stdlib packages (fetch_macholib) and bundle-wide executable audit, ICMP and Local Network privacy: does ICMP echo to an on-link host count?, Info.plist hygiene for py2app builds (PythonInfoDict developer path, NSAppleScriptEnabled), Interaction of the Local Network prompt with the screen-recording demo script (timer fire date, restart-only settings), Notes for Review dormant-feature disclosure patterns and a template library, Observing Local Network decisions: nehelper and mDNSResponder log predicates, fresh-account and VM procedures, Purpose-string review under 5.1.1(ii): wording for conditional features, Responsible-process attribution for setuid children (/sbin/ping) under App Sandbox and Local Network privacy, Source versus bytecode versus zip for first-party code: visibility to reviewers and scanners, Splitting failover.py into read-only listing and write path (Tier 3), Splitting privileges.py into constants and actions so the actions can be omitted (Tier 2), Staged-source build: run py2app on a pruned copy of the package instead of deleting afterwards, What runs at upload (altool/Transporter validation) versus at review (string and symbol scans): a timeline per guideline, com.apple.network.local-network allow-list defaults (AllowedWiFiLocalNetworkAddresses) for review-network testing, network.server justification patterns when the listener is user-enabled (2.4.5(i) precedents), py2app recipes that force packages in (detect_dunder_file) and how to override them