The earlier review correctly identified a reachable default self-update that downloads and executes a newer release. Current rules classify updating the same package from npm as suspicious when an off switch exists; NEVELA_NO_SELF_UPDATE is that switch, so this should be downgraded to a warning rather than blocked.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI to create an app, when a newer version exists and NEVELA_NO_SELF_UPDATE is unset.
Impact
Code from the newer release runs with the user’s permissions. Under the current self-update rule, updating this same package from npm with an off switch warrants a warning, not a publish block.
Mechanism
The CLI queries the package’s latest version, downloads its npm tarball, extracts it under the system temporary directory, and launches its index.mjs with the original arguments.
Evidence
index.mjsselfupdate.mjs/tmp/create-nevela-${version}-${pid}/package/index.mjs
Network endpoints2
registry.npmjs.org/create-nevela/latestregistry.npmjs.org/create-nevela/-/create-nevela-${version}.tgz