The manifest has no install lifecycle scripts, and the flagged execution and network behavior is tied to CLI features with expected purposes. I found no credential theft, unrelated collection endpoint, or concealed automatic execution.
Static reason
One or more suspicious static signals were detected.
Trigger
User runs the corresponding CLI command; no install hook runs these actions automatically.
Impact
Expected project update, app health-check, and package-validation effects; no malicious data flow was found.
Mechanism
Project updates can revise manifests and invoke npm install; the Nix helper can check a configured app health endpoint; package verification loads provider modules for validation.
Evidence
scripts/project-install.mjsscripts/project-packages.mjsscripts/nix-app.mjsscripts/verify-packages.mjs
Network endpoints1
{HOST}:{PORT}/api/health (defaults to http://127.0.0.1:3000/api/health)