hetzbot-node

Automate idempotent Node.js LTS installation with pinned versions and npm lockdown.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/tomspiegl/hetzbot --skill hetzbot-node
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hetzbot-node
Source: https://github.com/tomspiegl/hetzbot/tree/main/skills/runtimes/node
Command: npx skills add https://github.com/tomspiegl/hetzbot --skill hetzbot-node

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill installs Node.js LTS on a host with hardened npm defaults, ensuring consistent runtime and safer npm usage across the fleet.

Core Features & Use Cases

  • Pin Node major version (currently 20) to ensure stable upgrades.
  • Write host-wide /etc/npmrc with ignore-scripts, audit-level, and safe defaults.
  • Integrate with unattended-upgrades for automatic security patches from NodeSource.
  • Idempotent deployment: safe to run multiple times without unnecessary changes.

Quick Start

Install Node.js LTS on a host and ensure node-specific npm lockdown is in effect.

Frequently Asked Questions about hetzbot-node

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I securely install Node.js LTS and harden npm defaults on a host?

Secure Node.js LTS installation is automated by pinning a major version, writing a host-wide /etc/npmrc with ignore-scripts and audit-level, and integrating unattended-upgrades for consistent, safer runtime across deployments.

What does ignore-scripts in npmrc do for Node.js deployment security?

The ignore-scripts setting in a host-wide /etc/npmrc prevents npm packages from automatically executing installation scripts, hardening Node.js deployment security against malicious code execution during dependency installation.

Can I run Node.js LTS installation multiple times without breaking my environment?

Yes, the Node.js LTS installation is idempotent, meaning it verifies existing installation state and applies safety checks without making unnecessary changes, allowing safe repeated runs across your fleet.

Does Node.js LTS integrate with unattended-upgrades for automatic security patches?

Yes, this approach integrates Node.js LTS with unattended-upgrades to automatically apply security patches from NodeSource, ensuring your runtime stays updated without manual intervention.

What is the benefit of pinning a major Node.js version for fleet deployments?

Pinning a major Node.js version, currently 20, ensures stable and consistent upgrades across deployments by preventing unexpected breaking changes from major runtime version jumps.

What npm lockdown settings are enforced for secure Node.js runtime?

Host-wide npm lockdown enforces settings like ignore-scripts and audit-level in /etc/npmrc, establishing safe defaults that verify installation state and upgrade readiness for safer npm usage.