Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

Plugins no longer use npmResolution for provenance or trust

The npmResolution field is gone from plugin provenance, and plugins are no longer trusted on the basis of an npmResolution check

Group of 2 You'll notice Removed
JSON All of v2.1.323
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
RemovedKind: in v2.1.323,
RemovedSection of the release

What

Claude Code keeps a provenance record for each installed plugin, which is a note of where the plugin came from. That record no longer has an npmResolution field. The field held the npm packageName and tarballUrl, and it has been removed from both the schema (the definition of what the record may contain) and the code that builds the record.

The trust check changed along with it:

  • The plugin trust function no longer has a case that treated a plugin as trusted when its npmResolution passed a check.

Why

Plugins installed from npm are no longer recorded with these npm details, and those details no longer make a plugin trusted. If you relied on npm-sourced plugins being trusted this way, other criteria now decide whether they are trusted.

See this entry in the whole of v2.1.323 →

Feedback