diff --git a/docs/_components/VersionSpecifierTable.mdx b/docs/_components/VersionSpecifierTable.mdx index 7cd27d6..43a6b53 100644 --- a/docs/_components/VersionSpecifierTable.mdx +++ b/docs/_components/VersionSpecifierTable.mdx @@ -1,9 +1,10 @@ | Form | Example | Resolution | |------|---------|------------| -| Latest release | `latest` | Newest available release from the mirror index. | +| Latest stable | `latest` | Newest **stable** (non-prerelease) release from the mirror index. Skips tags that contain `-` (for example alphas). | +| Latest alpha | `alpha` | Newest release whose version contains `-alpha`. Keeps the full prerelease tag for download. | | Latest LTS | `lts` | Newest available LTS release. | | Named LTS line | `lts/iron` | Newest release from the named LTS line. | | User alias | `legacy` | Version assigned with [`nvm alias add`](../command/nvm/alias/add). | | Major only | `24` | Newest matching `24.x.x` release. | | Major.minor | `24.1` | Newest matching `24.1.x` release. | -| Exact version | `24.1.0`, `v24.1.0` | The specified release. The `v` prefix is optional. | \ No newline at end of file +| Exact version | `24.1.0`, `v24.1.0`, `27.0.0-alpha.0.0.0` | The specified release. The `v` prefix is optional. Prerelease suffixes are preserved. | \ No newline at end of file diff --git a/docs/_data/siemQueries.js b/docs/_data/siemQueries.js index ac5402f..db13d9c 100644 --- a/docs/_data/siemQueries.js +++ b/docs/_data/siemQueries.js @@ -114,6 +114,42 @@ export const siemQueries = { | STATS People = COUNT_DISTINCT(winlog.computer_name)`, wevtutil: `wevtutil qe "${CHANNEL}" /q:"*[System[(EventID=120)] and EventData[Data[@Name='EventName']='nvm.system.changed']]" /f:text /c:20`, }, + unstableInstalled: { + wevtutilListsOnly: true, + sentinel: `Event +| where EventLog == "${CHANNEL}" +| where EventID == 120 +| where EventData.EventName == "nvm.system.changed" +| extend Payload = parse_json(tostring(EventData.Payload)) +| where Payload.Action == "install" +| where Payload.Outcome == "Succeeded" +| where tostring(Payload.ReleaseType) == "unstable" +| summarize Hosts = dcount(tostring(Payload.hostname)) by tostring(Payload.NodeVersion), tostring(Payload.hostname)`, + splunk: `index=wineventlog Channel="${CHANNEL}" EventCode=120 EventData.EventName="nvm.system.changed" +| eval action=json_extract('EventData.Payload',"Action"), outcome=json_extract('EventData.Payload',"Outcome"), release_type=json_extract('EventData.Payload',"ReleaseType"), node_version=json_extract('EventData.Payload',"NodeVersion"), hostname=json_extract('EventData.Payload',"hostname") +| search action=install outcome=Succeeded release_type=unstable +| stats dc(hostname) as Hosts by node_version, hostname`, + elastic: `FROM logs-* +| WHERE winlog.channel == "${CHANNEL}" AND winlog.event_id == 120 AND winlog.event_data.EventName == "nvm.system.changed" AND winlog.event_data.Payload LIKE "*\\"Action\\":\\"install\\"*" AND winlog.event_data.Payload LIKE "*\\"Outcome\\":\\"Succeeded\\"*" AND winlog.event_data.Payload LIKE "*\\"ReleaseType\\":\\"unstable\\"*" +| STATS Hosts = COUNT_DISTINCT(winlog.computer_name)`, + wevtutil: `wevtutil qe "${CHANNEL}" /q:"*[System[(EventID=120)] and EventData[Data[@Name='EventName']='nvm.system.changed']]" /f:text /c:20`, + }, + legacyLatestHosts: { + wevtutilListsOnly: true, + sentinel: `Event +| where EventLog == "${CHANNEL}" +| where EventID == 120 +| where EventData.EventName == "nvm.resolution.legacy_latest" +| extend Payload = parse_json(tostring(EventData.Payload)) +| summarize Events = count() by tostring(Payload.hostname), tostring(Payload.ResolvedVersion)`, + splunk: `index=wineventlog Channel="${CHANNEL}" EventCode=120 EventData.EventName="nvm.resolution.legacy_latest" +| eval hostname=json_extract('EventData.Payload',"hostname"), resolved=json_extract('EventData.Payload',"ResolvedVersion") +| stats count as Events by hostname, resolved`, + elastic: `FROM logs-* +| WHERE winlog.channel == "${CHANNEL}" AND winlog.event_id == 120 AND winlog.event_data.EventName == "nvm.resolution.legacy_latest" +| STATS Events = COUNT(*) BY host = winlog.computer_name`, + wevtutil: `wevtutil qe "${CHANNEL}" /q:"*[System[(EventID=120)] and EventData[Data[@Name='EventName']='nvm.resolution.legacy_latest']]" /f:text /c:20`, + }, uninstalledVersions: { wevtutilListsOnly: true, sentinel: `Event diff --git a/docs/cfg/aliases.md b/docs/cfg/aliases.md index 10c8f2c..9f3b8fb 100644 --- a/docs/cfg/aliases.md +++ b/docs/cfg/aliases.md @@ -107,7 +107,8 @@ next -> v24.11.0 | Name | Why | |:-|:-| | `default`, `current`, `latest`, `lts`, `last` | Built-in command semantics | -| `daily`, `alpha`, `beta`, `prerelease` | Reserved for future use | +| `alpha` | Built-in: newest `-alpha*` catalog release | +| `daily`, `beta`, `prerelease` | Reserved for future use | | `link`, `shim` | Operating mode names | | `lts/*` (for example `lts/iron`) | Reserved LTS namespace | diff --git a/docs/cfg/enterprise/registry.md b/docs/cfg/enterprise/registry.md index 5bc6c7d..adaf2f9 100644 --- a/docs/cfg/enterprise/registry.md +++ b/docs/cfg/enterprise/registry.md @@ -93,8 +93,9 @@ These keys appear in the **Governance** ADMX pack. The Policies hive (including |**Approved modules (local installs)**|`ApprovedModules`|**Certified Builds.** Shim mode. Allow list for local package-manager installs (npm/pnpm/yarn/npx). Empty defaults to `ALL`. Supports name, `@org/*`, version pins/ranges, `NOT`/`!` negation, or a single `https://` policy URL. See [NVM Firewall](/features/firewall).

`REG_MULTI_SZ`| |**Approved global modules**|`ApprovedGlobalModules`|**Certified Builds.** Shim mode. Allow list for global package-manager installs. Empty defaults to `ALL`. Same rule syntax as `ApprovedModules`.

`REG_MULTI_SZ`| |**Untrusted module change action**|`UntrustedModuleHandlerAction`|Shim mode. When a global module changes and is not on `TrustedModules`:

- `deny` (default) — skip reshim
- `prompt` — console or Trust/Cancel toast
- `allow` — auto-reshim with a quiet toast

`REG_SZ`| -|**Allowed Node.js versions**|`VersionAllowList`|**Governance.** Allow list for `nvm install`, `nvm use`, and the shim. Ignored without a Governance license. Invalid entries fail enforcement. Allow wins over block when both lists come from the same source. The shim loads allow and block as a pair from HKLM Policies when Governance is active. Also feeds Author-mirror JWT version claims (magic tokens such as `EOL`, `ALPHA`, `MAINTENANCE`, `ALL`). Those magic tokens are ignored locally at install, use, and shim launch.

Supports exact semver, wildcards (e.g. `20.x`), aliases, and `NOT`/`!` negation (one rule per line).

`REG_SZ`| -|**Blocked Node.js versions**|`VersionBlockList`|**Governance.** Block list for `nvm install`, `nvm use`, and the shim. Same rule formats and pairing as `VersionAllowList`. Ignored without Governance.

`REG_SZ`| +|**Allowed Node.js versions**|`VersionAllowList`|**Governance.** Allow list for `nvm install`, `nvm use`, and the shim. Ignored without a Governance license. Invalid entries fail enforcement. Allow wins over block when both lists come from the same source. The shim loads allow and block as a pair from HKLM Policies when Governance is active. Also feeds Author-mirror JWT version claims (`EOL`, `ALPHA`, `MAINTENANCE`, `ALL`). **`ALPHA` is enforced locally** against versions containing `-alpha`. **`EOL` and `MAINTENANCE` remain mirror-only** (ignored by local gates).

Supports exact semver, wildcards (e.g. `20.x`), aliases, and `NOT`/`!` negation (one rule per line).

`REG_SZ`| +|**Blocked Node.js versions**|`VersionBlockList`|**Governance.** Block list for `nvm install`, `nvm use`, and the shim. Same rule formats and pairing as `VersionAllowList`. Ignored without Governance. `ALPHA` blocks local alpha installs (for example `nvm install alpha`).

`REG_SZ`| +|**Legacy tip-of-index latest**|`LatestIncludesPrerelease`|**Governance.** When `1`, the reserved `latest` alias resolves to the absolute tip of the Node.js index (including prereleases). Default `0` = newest stable only. Machine policy only. Emits `nvm.resolution.legacy_latest` when used. See [Legacy latest policy](/guide/legacy-latest-policy).

- `0` = stable `latest` (default)
- `1` = tip-of-index (legacy)

`REG_DWORD`| :::info[License secrets] `AccessToken`, `AccessKey`, and `JwksCose` are **not** ADMX policies. Deploy with portal scripts (`Set-NvmWindowsAccessToken.ps1` on stock certified build; `Set-NvmWindowsLicensing.ps1` for governance builds, which also sets `AccessKey` for Author mirrors) or `nvm license`. diff --git a/docs/command/nvm/install/index.md b/docs/command/nvm/install/index.md index e9eb5bd..6df4b36 100644 --- a/docs/command/nvm/install/index.md +++ b/docs/command/nvm/install/index.md @@ -12,10 +12,10 @@ Install one or more versions of Node.js. ## Usage ```powershell -nvm install [ ...] [flags] +nvm install [ ...] [flags] ``` -Default subcommand when you pass version arguments directly (for example `nvm install 24`). +Default subcommand when you pass version arguments directly (for example `nvm install 24`). With no version, installs `latest` (newest stable release) — same as `nvm install latest`. ## Subcommands @@ -28,7 +28,7 @@ Default subcommand when you pass version arguments directly (for example `nvm in | Argument | Required | Description | |----------|----------|-------------| -| ` ...` | Yes | One or more [version specifiers](../../../guide/version-resolution). | +| ` ...` | No | One or more [version specifiers](../../../guide/version-resolution). Omit to install `latest` (stable). | ## Flags @@ -46,7 +46,10 @@ Internal flags (`--notify`, `--debug`) exist for automation and are hidden from ## Examples ```powershell +nvm install +nvm install latest nvm install lts +nvm install alpha nvm install 24 nvm install 22.14.0 20.19.1 nvm install lts/iron diff --git a/docs/features/all-features.md b/docs/features/all-features.md index dc21582..700ee15 100644 --- a/docs/features/all-features.md +++ b/docs/features/all-features.md @@ -151,7 +151,7 @@ See [What's new in v2](./newv2) for a shorter v2 summary. | Community feature mode | A Certified Build without a commercial license keeps running with Community features. | | License | Hidden `nvm license` writes HKLM. Certified Builds, Advanced Logging, and Governance need a sitewide license. | | License expiry notifications | Certified Builds warn at 7, 3, and 1 day, on the expiry day, and daily in the 7-day grace window. | -| [Author Mirror](./author-mirror) | Governance host `https://mirror.author.io/runtime/nodejs`. JWT version lists. EOL/ALPHA/MAINTENANCE need this host. | +| [Author Mirror](./author-mirror) | Governance host `https://mirror.author.io/runtime/nodejs`. JWT version lists. `ALPHA` is also enforced locally; `EOL`/`MAINTENANCE` need this host. | | [Basic HTTP proxy](./http-proxy) | Proxy URL, `user:pass`, or Bearer. WinINET fallback. Community Builds and Certified Builds. | | [Advanced proxy](./http-proxy#capabilities-by-license) | IWA (NTLM/Negotiate) and PAC/WPAD. [Governance](./certified-builds/governance) add-on. | | Administrative templates | ADMX/ADML lock or override preferences. See [Administrative Templates](../cfg/ad) and [Governance](./certified-builds/governance). | diff --git a/docs/features/author-mirror.md b/docs/features/author-mirror.md index 4c5d1fe..96992dc 100644 --- a/docs/features/author-mirror.md +++ b/docs/features/author-mirror.md @@ -58,7 +58,7 @@ There are two (combinable) ways to enforce dynamic policies on the Author mirror `VersionAllowList` / `VersionBlockList` (see [Governance registry keys](/cfg/registry#governance-keys)) do double duty: - **Static entries** — enforced by [NVM Firewall](./firewall) before any download. -- **Dynamic aliases** (`EOL`, `ALPHA`, `MAINTENANCE`) — ignored on the client; included in the short-lived license JWT sent only to `mirror.author.io`. The mirror applies those lifecycle rules when serving the archive. +- **Dynamic aliases** — `ALPHA` is enforced locally against versions containing `-alpha` and is also included in the short-lived license JWT sent to `mirror.author.io`. `EOL` and `MAINTENANCE` are ignored on the client; the mirror applies those lifecycle rules when serving the archive. | Policy entry | Local client | Author mirror (`mirror.author.io`) | Public mirror (`nodejs.org`) | |:-|:-|:-|:-| diff --git a/docs/guide/builds/index.md b/docs/guide/builds/index.md index 225890f..dd6ff68 100644 --- a/docs/guide/builds/index.md +++ b/docs/guide/builds/index.md @@ -77,7 +77,7 @@ The Governance package for Certified Builds introduce policy management. With th - Freeze V8 intrinsics (`--frozen-intrinsics`) to prevent prototype pollution of built-ins (also applied to npm/npx/pnpm scripts when the policy is on). - Disallow `eval()` / `new Function()` (`--disallow-code-generation-from-strings`) (also applied to npm/npx/pnpm scripts when the policy is on). - Limit to local installations (airgapping). -- Restrict version installations with the version firewall. Lifecycle aliases such as `EOL` and `ALPHA` apply on the Author Mirror, not the client. +- Restrict version installations with the version firewall. `ALPHA` is enforced locally; `EOL` and `MAINTENANCE` apply on the Author Mirror. Governance builds ship with ADMX/ADML files and official scripts to support Microsoft Active Directory group policies, Microsoft Entra, and other device management platforms. diff --git a/docs/guide/legacy-latest-policy.md b/docs/guide/legacy-latest-policy.md new file mode 100644 index 0000000..dbe7b4d --- /dev/null +++ b/docs/guide/legacy-latest-policy.md @@ -0,0 +1,68 @@ +--- +title: Legacy latest policy +sidebar_label: Legacy latest policy +sidebar_position: 2.5 +--- + +# Legacy latest policy + +On Certified Builds with a **Governance** license, administrators can restore the older tip-of-index meaning of the reserved `latest` alias without changing scripts. + +By default in v2, `nvm install latest` and `nvm use latest` resolve to the newest **stable** (non-prerelease) Node.js release. That avoids installing alphas that temporarily lead [nodejs.org/dist/index.tab](https://nodejs.org/dist/index.tab). + +Some fleets still have automation that expects `latest` to mean “whatever sits at the tip of the catalog,” including prereleases. The Governance policy below keeps those scripts working while logging hosts that still rely on that behavior. + +## Policy + +| Item | Value | +|------|--------| +| Registry | `HKLM\SOFTWARE\Policies\Author Software\nvm\LatestIncludesPrerelease` | +| Type | `REG_DWORD` | +| Default | `0` (stable `latest`) | +| Enabled | `1` (tip-of-index, including prereleases) | +| Scope | Machine policy only (no HKCU preference) | +| License | Governance | + +Deploy with the Governance ADMX (**Use legacy tip-of-index for latest**) or Intune/Registry CSP. + +Community Builds ignore this key. Without Governance, the key has no effect. + +## Behavior when enabled + +1. `latest` resolves to the first non-empty row of the Node.js index, **keeping** any prerelease suffix (for example `27.0.0-alpha.0.0.0`). +2. Scripts keep the same command shape: `nvm install latest`. +3. NVM writes a structured warning: EventName `nvm.resolution.legacy_latest`. +4. Successful installs driven by `latest` under this policy also set `LatestMode=legacy` on `nvm.system.changed`. + +Prefer migrating callers to: + +```powershell +nvm install alpha +# or +nvm install 26.13.0 +``` + +`alpha` is the explicit reserved alias for the newest `-alpha*` release. + +## Interaction with the version firewall + +`LatestIncludesPrerelease` does **not** bypass Governance version lists. + +If `VersionBlockList` contains `ALPHA`, an install of an alpha (including one reached via legacy `latest`) is still denied locally (**NVM4411**). + +See [Version Firewall + Author Mirror](../features/author-mirror) and [Registry Policy Reference](../cfg/enterprise/registry). + +## SIEM + +Use the SIEM guide queries for: + +- Hosts that resolved `latest` under legacy mode (`nvm.resolution.legacy_latest`) +- Installs with `ReleaseType=unstable` or `LatestMode=legacy` + +See [SIEM Integration](./siem). + +## Related + +- [Version Resolution](./version-resolution) — `latest` vs `alpha` +- [Upgrading from v1](./upgrade-from-v1) +- [Registry Policy Reference](../cfg/enterprise/registry) diff --git a/docs/guide/security.md b/docs/guide/security.md index 4c61243..bcaeae0 100644 --- a/docs/guide/security.md +++ b/docs/guide/security.md @@ -205,7 +205,7 @@ The **Governance** pack ships **ADMX/ADML** templates for Active Directory and E Organizations can deny public `nodejs.org/dist` at the network edge and allow-list `mirror.author.io`. NVM then downloads through Author’s policy-aware mirror. Controls combine: -- Client/GPO lists (`VersionAllowList` / `VersionBlockList`) for exact versions and ranges — lifecycle aliases such as `EOL` / `ALPHA` / `MAINTENANCE` are **ignored on the client** and only applied by the Author Mirror at download +- Client/GPO lists (`VersionAllowList` / `VersionBlockList`) for exact versions and ranges — `ALPHA` is enforced locally against `-alpha*` versions; `EOL` / `MAINTENANCE` are **ignored on the client** and only applied by the Author Mirror at download - **Hosted rules** in the [customer portal](https://portal.author.io) (IP, geo, domain/tenant, SID, license group) Walkthrough: [Version Firewall + Author Mirror](../features/author-mirror). Domain/tenant IDs: [Find Your AD Domain or Entra Tenant ID](./find-domain-tenant-id). diff --git a/docs/guide/siem.md b/docs/guide/siem.md index 6cfaef3..f3f6252 100644 --- a/docs/guide/siem.md +++ b/docs/guide/siem.md @@ -81,6 +81,12 @@ Host count for the same event: +`nvm.system.changed` payloads include `ReleaseType` (`stable` or `unstable`). Unstable means the Node.js version string contains a prerelease suffix (any `-`). + +### Hosts with unstable Node.js installs + + + ### Who installed Node.js 20 @@ -88,6 +94,12 @@ Host count for the same event: Change `20.` to another major version, or to an EOL line your policy tracks. The event does not mark EOL for you. +### Hosts still using legacy `latest` + +Governance `LatestIncludesPrerelease` writes `nvm.resolution.legacy_latest` when `latest` resolves to tip-of-index. Successful installs also set `LatestMode=legacy` on `nvm.system.changed`. See [Legacy latest policy](./legacy-latest-policy). + + + ### Who uninstalled a Node.js version @@ -162,7 +174,8 @@ Query these by `EventName`. | EventName | What it records | |:-|:-| -| `nvm.system.changed` | Install, uninstall, and similar lifecycle results. Payload: `Action`, `NodeVersion`, `Outcome`, `User`, `sid`, `hostname`, `correlation_id`. | +| `nvm.system.changed` | Install, uninstall, and similar lifecycle results. Payload: `Action`, `NodeVersion`, `ReleaseType` (`stable` \| `unstable`), `Outcome`, `User`, `sid`, `hostname`, `correlation_id`. Installs driven by `latest` under Governance `LatestIncludesPrerelease` also include `LatestMode=legacy`. | +| `nvm.resolution.legacy_latest` | Warning when reserved `latest` resolves under Governance `LatestIncludesPrerelease`. Payload: `ResolvedVersion`, `LatestMode`, `User`, `hostname`, `Detail`. | | `nvm.configuration.changed` | A setting change. Payload: `Configuration`, `Value`, `Old`, `Outcome`. | | `nvm.version.activated` | The active Node.js version changed. Payload: `version`, `previous_version`, `user`, `hostname`. | | `nodejs.executed` | A `node` launch when `LogExecutions` is `1`. Source `node-shim`. When permission allow flags were supplied, applied, or removed, the payload includes `permission_allow.supplied`, `permission_allow.applied`, and `permission_allow.removed`. | diff --git a/docs/guide/upgrade-from-v1.md b/docs/guide/upgrade-from-v1.md index 1a59fa3..214e444 100644 --- a/docs/guide/upgrade-from-v1.md +++ b/docs/guide/upgrade-from-v1.md @@ -61,6 +61,12 @@ Installed Node.js versions from a supported v1 install are merged into v2 storag You do not re-download those versions when the copy succeeds. After install, open a **new** terminal and run `nvm list` to confirm the versions. +### `latest` alias + +In v2, `nvm install latest` resolves to the newest **stable** Node.js release (it skips prereleases such as alphas). +Use `nvm install alpha` for the newest `-alpha*` release. +Governance fleets that must keep tip-of-index `latest` for existing scripts can enable `LatestIncludesPrerelease` — see [Legacy latest policy](./legacy-latest-policy). + ### Backup in restricted environments The installer copies Node.js version trees and related files during migration. diff --git a/docs/guide/version-resolution.md b/docs/guide/version-resolution.md index 6f375e5..160d09a 100644 --- a/docs/guide/version-resolution.md +++ b/docs/guide/version-resolution.md @@ -35,12 +35,21 @@ Commands that accept version specifiers include: - [`nvm cache add`](../command/nvm/cache/add) - [`nvm cache remove version`](../command/nvm/cache/remove/version) +### `latest` vs `alpha` + +- `latest` walks the Node.js index and picks the newest row **without** a `-` prerelease suffix. When Node publishes an alpha at the tip of [index.tab](https://nodejs.org/dist/index.tab), `latest` still resolves to the prior stable release so downloads do not invent a missing GA tag. Bare `nvm install` (no version argument) is the same as `nvm install latest`. +- `alpha` picks the newest row whose version contains `-alpha` and keeps that full tag (for example `27.0.0-alpha.0.0.0`) for download and install. After `nvm install alpha` succeeds, NVM prints a one-line note that alpha releases are unstable. + +Governance fleets that must keep the older tip-of-index meaning of `latest` can enable `LatestIncludesPrerelease`. See [Legacy latest policy](./legacy-latest-policy). + ### Examples ```powershell # reserved aliases +nvm install nvm install lts nvm use latest +nvm install alpha # named LTS line nvm install lts/iron @@ -88,7 +97,7 @@ Example: default `13.14.0`, `engines.node` is `>=20`. `13.14.0` does not satisfy ## Resolution order {/* #resolution-order */} 1. User alias mapping (from `nvm alias add`) -2. Reserved aliases (`latest`, `lts`, `lts/`) +2. Reserved aliases (`latest`, `alpha`, `lts`, `lts/`) 3. Partial versions expanded to the best matching concrete release 4. Semver constraints resolved in constraint-aware flows (for example `engines.node` or caret/tilde ranges in detect files) 5. Read version string from the configured detect file in the current directory tree (auto-detect) diff --git a/docs/troubleshooting/error-codes.md b/docs/troubleshooting/error-codes.md index bd2509b..0fdf45f 100644 --- a/docs/troubleshooting/error-codes.md +++ b/docs/troubleshooting/error-codes.md @@ -47,7 +47,7 @@ NVM for Windows uses stable `NVM####` codes in CLI messages, shim/proxy output, | **NVM4406** | Untrusted module changed | Audit (non-error): untrusted global CLI entrypoint changed; logged for deny, allow, and prompt accept/decline | | **NVM4408** | Module firewall allowed install | Audit (non-error): Governance module lists allowed the install. Certified Builds write structured event `package_manager.install` (richer `EventName` / `Payload` with Advanced Logging). | | **NVM4410** | Firewall policy mutated | Audit: `nvm firewall` changed a policy list | -| **NVM4411** | Version firewall blocked a Node.js version | Governance `VersionAllowList` / `VersionBlockList` denied `nvm install`, `nvm use`, or a shim launch. Without Governance those lists are ignored. Lifecycle aliases such as `EOL` do not trigger this on the client. | +| **NVM4411** | Version firewall blocked a Node.js version | Governance `VersionAllowList` / `VersionBlockList` denied `nvm install`, `nvm use`, or a shim launch. Without Governance those lists are ignored. `ALPHA` is enforced locally against `-alpha*` versions. `EOL` / `MAINTENANCE` do not trigger this on the client. | | **NVM4412** | Package-manager lifecycle scripts blocked | Audit (non-error), Advanced Logging on Certified Builds only. HKLM `BlockPackageManagerLifecycleScripts` rewrote an install-class command (`install` / `ci` / `add` / …). `npm --version` and `npm run` do not write this event. EventName `package_manager.lifecycle_scripts_blocked`. Windows Event ID 120 | | **NVM4501** | Network deadline exceeded | Informational: a catalog, mirror, reachability, or download attempt used up its millisecond budget. Structured event `network.deadline_exceeded` (Certified Builds with Advanced Logging) | | **NVM4601** | Malware definitions updated | Informational, advanced logging only. A successful `malware.db` write changed the database. Payload: `added`, `removed`, `seq`, `previous_seq`. Windows Event ID 120 |