nvm-defaults-and-nvmrc

Pass

Audited by Gen Agent Trust Hub on Oct 6, 2026

Risk Level: SAFEINDIRECT_PROMPT_INJECTIONPERSISTENCE
Full Analysis
  • [INDIRECT_PROMPT_INJECTION]: The skill provides examples for shell hooks that automatically read and act upon the contents of .nvmrc files when entering a directory.\n
  • Ingestion points: The shell logic in examples/auto-use-bash.md, examples/auto-use-zsh.md, and examples/auto-use-fish.md searches for and reads the contents of local .nvmrc files.\n
  • Boundary markers: The snippets do not implement specific boundary markers or safety delimiters for the content of the .nvmrc file before passing it to the shell function.\n
  • Capability inventory: The content of the file is used as an argument to nvm install and nvm use commands which can install and execute Node.js versions.\n
  • Sanitization: The scripts rely on the validation logic of the nvm tool itself to verify the version strings read from the file.\n- [PERSISTENCE]: The skill provides examples for adding automated hooks to shell configuration files (.bashrc, .zshrc, or config.fish).\n
  • Evidence: The provided shell code uses directory change hooks (like chpwd in Zsh or cdnvm alias in Bash) to ensure the version switching logic persists across terminal sessions and directory changes. This persistence is standard for the tool's intended use case and does not represent a malicious intent.
Audit Metadata
Risk Level
SAFE
Analyzed
Oct 6, 2026, 01:34 PM