OpenClaw plugins.installs_unpinned_npm_specs and Related Install Findings

Published 2026-10-20 · Updated 2026-10-20 · By The Is My Agent Safe team

Short answer

An npm-installed plugin or hook pack is recorded without an exact version, so a later update can install whatever version the registry offers then. It's a warning, not a sign that anything bad was installed. To fix it, update each listed plugin to an exact version, for example openclaw plugins update <package>@1.2.3, then run openclaw security audit --deep again.

  • OpenClaw rates all three install findings warn, for plugins and for hook packs.
  • unpinned_npm_specs: the recorded install spec has no exact version. missing_integrity: there's no integrity hash. version_drift: the recorded version doesn't match what's installed.
  • Fix: pin an exact version with openclaw plugins update <package>@<version>, or install with --pin. For missing integrity or drift, run openclaw plugins update --all.
  • Two open GitHub reports (#176136 and #164162) say the unpinned warning appears for records that already hold an exact resolved version. OpenClaw's maintainers haven't confirmed either or shipped a fix.

Paste your audit: run openclaw security audit --deep and paste the output into our free check for a red/amber/green result with the most important finding first (Limits of the check).

What should I do first?

Read the finding's detail. It lists each plugin and its recorded spec. Made-up example:

Unpinned plugin index install records:
- my-plugin (example-plugin)

Pin each one to the exact version you want:

openclaw plugins update <package>@1.2.3 --dry-run   # preview
openclaw plugins update <package>@1.2.3
openclaw security audit --deep

OpenClaw's update docs say that when you pass an npm spec with an exact version, OpenClaw "resolves that package name back to the tracked plugin record, updates that installed plugin, and records the new npm spec for future id-based updates". To install a new plugin pinned from the start, the install docs show openclaw plugins install npm:<package> --pin, which "records the resolved exact <name>@<version>". --pin works for npm installs only.

Hook packs are installed with the same command, so the same fix applies to hooks.installs_unpinned_npm_specs. The hooks docs show openclaw plugins install npm:<package>@<version> --pin.

When the audit comes back without the finding, you're done with it. OpenClaw's update docs say exact pins on third-party plugins are kept, so those plugins don't move to new releases on their own. Check for updates yourself. Some exact pins on official OpenClaw plugins can resume automatic updates during an update, which may bring the warning back (see below). See how to update OpenClaw without breaking it.

What do these findings mean?

OpenClaw's security audit checks page lists six install findings, all warn:

checkIdOpenClaw's description
plugins.installs_unpinned_npm_specs"Plugin index records are not pinned to immutable npm specs"
plugins.installs_missing_integrity"Plugin index records lack integrity metadata"
plugins.installs_version_drift"Plugin index records drift from installed packages"
hooks.installs_unpinned_npm_specs"Hook install records are not pinned to immutable npm specs"
hooks.installs_missing_integrity"Hook install records lack integrity metadata"
hooks.installs_version_drift"Hook install records drift from installed packages"

In OpenClaw 2026.10.5's source, these checks look only at npm installs:

OpenClaw's suggested fixes, from the audit output:

For hook packs, the drift fix is openclaw hooks update --all.

Why does it matter?

An unpinned spec means the next update installs whatever version the registry then offers. OpenClaw's update docs say that when a stored integrity hash exists and the downloaded file's hash changes, the interactive openclaw plugins update "prints the expected and actual hashes and asks for confirmation before proceeding". A record without an integrity hash doesn't get that comparison.

None of these findings means a plugin is harmful. OpenClaw checks plugin code separately. See plugins.code_safety findings.

Could it be a false alarm?

Partly, for the unpinned finding. The recorded spec is what future updates follow, so on these records the warning still describes how the plugin will update, even when the installed version is exact. Two open GitHub reports describe it:

OpenClaw's maintainers haven't confirmed either report or shipped a fix. The update docs describe the behavior behind #164162: some exact pins on official OpenClaw plugins "resume automatic updates", while pins on third-party packages are kept. So a pin you set on an official plugin may not stay, and the warning may come back after an update.

If the listed plugin is an official OpenClaw plugin and you're happy following OpenClaw's release line, you can treat this warning as expected. For third-party plugins, pin them. Our guide to audit false alarms explains how to record a deliberate choice.

What our free check covers

The free check at /check is paste-only. We check the text you paste: your openclaw security audit output. The check never connects to your Gateway or downloads your plugins, so it can't check which versions are installed. Nothing is installed into the agent you're checking. Green means no issues found in the checks we ran.

The free check puts the most important finding first, in plain English. The full report explains every finding and lists the fixes in order. The check doesn't detect malicious skills. We don't review the code inside skills or MCP servers ourselves, beyond what OpenClaw's own audit reports. The check is free, and a full report is $29. See Limits of the check.

Frequently asked questions

What does plugins.installs_unpinned_npm_specs mean?

At least one npm plugin is recorded with a spec that has no exact version, such as a bare package name or a tag. OpenClaw rates it warn and suggests pinning "for higher supply-chain stability". The detail lists each plugin and its recorded spec.

How do I fix plugins.installs_unpinned_npm_specs?

For each plugin listed, run openclaw plugins update <package>@<exact-version> (OpenClaw's docs say this records the new npm spec for future updates), or reinstall with openclaw plugins install npm:<package>@<version> --pin. Then re-run openclaw security audit --deep. For hook packs, do the same for each hook listed.

What do installs_missing_integrity and installs_version_drift mean?

missing_integrity means an install record has no integrity hash. version_drift means the recorded version doesn't match the installed package.json. OpenClaw suggests openclaw plugins update --all (or openclaw hooks update --all for hooks), or reinstalling the affected plugin.

Is the unpinned warning a false alarm?

Not exactly. Two open GitHub reports say the check only reads the recorded spec, so records that also hold an exact resolved version and an integrity hash are still flagged. The recorded spec is what future updates follow, so the warning still describes how that plugin will update. OpenClaw's maintainers haven't decided either report or shipped a change.

Can your free check see my plugins?

No. We check the text you paste, which is where this finding comes from. The check never connects to your Gateway or downloads your plugins, so it can't check which versions are installed.

Sources

  1. OpenClaw docs: security audit checks (checkId catalog)
  2. OpenClaw docs: openclaw plugins install (--pin scope)
  3. OpenClaw docs: openclaw plugins uninstall and update (pins and integrity drift)
  4. OpenClaw docs: openclaw hooks (hook packs)
  5. OpenClaw source v2026.10.5: src/security/audit-plugins-trust.ts (where the checks are defined)
  6. GitHub issue #176136 (open): pinned records flagged as unpinned
  7. GitHub issue #164162 (open): core update turns an exact spec into a floating spec