The network and file access serve the package’s documented purpose: preparing a project for an Expo Launch. The upload is disclosed in the CLI confirmation, and the only non-interactive bypass occurs when the user explicitly runs that launch command.
Static reason
One or more suspicious static signals were detected.
Trigger
The user runs the documented `launch` command; non-interactive or CI use skips the confirmation prompt.
Impact
The project files are sent to the Expo Launch service to prepare an app-store launch.
Mechanism
The CLI packages files beneath the current working directory and POSTs the archive to `LAUNCH_HOST`, defaulting to `launch.expo.dev`; Expo authentication is used for the Launch workflow.
Evidence
project files beneath process.cwd() (read for upload)~/.expo/state.json~/.expo-local/state.json~/.expo-staging/state.json
Network endpoints8
launch.expo.devapi.expo.devstaging-api.expo.dev127.0.0.1:3000