Things to check
Installations can run package lifecycle scripts and change package or lock files. A familiar package name does not verify its publisher or contents.
Before you run it
Review package.json, the lockfile, registry and lifecycle behavior before installing.
Ask your agent
“Explain the entire command, including every flag and operator. What exact files, services or permissions could it affect, and how will we verify the result?”
Context is part of the command
A command name alone cannot determine safety. Aliases, shell functions, expansions, flags, permissions and working directory can change its behavior.