4DPocket: why it is not safe to use
We found install-time remote script execution and sudo-based system setup, which adds host risk beyond a simple local app install.
What we found
Our review did not find hidden instructions, hardcoded live secrets, undisclosed data destinations, or obvious attempts to access unrelated credentials. The main concern came from how setup is handled. In the inspected repository, the install helper fetches and pipes remote installer or setup scripts for `uv` and Node.js. Those sources are named, but this still creates network-reachable install-time execution rather than a fully self-contained local setup.
We also found that the bundled `app.sh` uses `sudo` package-manager commands on Linux and can install system dependencies. That is broader host access than a simple app launch, and it means the setup process may make system-level changes. Separately, the app can call remote AI endpoints if the user chooses to configure them.
What to do instead
Prefer a manual install path where you review commands before running them, especially anything fetched over the network or piped to a shell. Use the skill in an isolated environment such as a container or VM if you want to limit host impact. If you enable external AI providers, configure only the endpoints and keys you intend to use, and avoid granting `sudo` unless you are comfortable with system-level package installation.
Source: https://github.com/onllm-dev/4DPocket
We report what our security review found at the time we checked, with the goal of keeping people safe. Projects change; if a maintainer has since fixed this, we are glad to recheck it. Email hello@agentpod.com.