The package’s default CLI path downloads and executes a newer release of itself from npm, passing it the caller’s full environment. The official registry and same-package update purpose lower the risk, but the automatic execution path warrants a warning because the code that runs may not be the inspected version.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the normal create command from an installed copy when npm reports a newer version; the upgrade command also checks for updates.
Impact
Newly downloaded package code runs with the user's privileges and environment without a separate update command; this snapshot cannot establish what a future release will do.
Mechanism
It fetches the package tarball, extracts it under the OS temporary directory, and launches its entry point with the caller's environment.
Evidence
index.mjsselfupdate.mjsOS temporary directory/create-nevela-${version}-${pid}
Network endpoints2
registry.npmjs.org/create-nevelaregistry.npmjs.org/create-nevela/-/create-nevela-${version}.tgz