Troubleshoot plugins changedplugins/troubleshooting
Nearest release: v2.1.287, published 5 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 1 Oct 2026 22:47 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 1 Oct 2026 23:07 UTC.
Upstream edited
Recorded here
Lines+15added
Lines−0removed
From line
450
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits13to this page, all time
The whole hunk
from line 450, old and new numbered
/
from line 450
450450* **You publish the plugin**: recompute the digest of the exact file the URL serves and update the `sha256` in the marketplace entry. Use `shasum -a 256 my-plugin.zip`, or `Get-FileHash -Algorithm SHA256 my-plugin.zip` in PowerShell
451451* **You install the plugin**: run `/plugin marketplace update <name>` in a session to refresh the catalog in case the entry was corrected, then retry the install. If the digests still disagree after the refresh, ask the marketplace owner which file they pinned before installing
452452
453<h3 id="an-npm-plugin-source-must-name-a-registry-package">
454 `An npm plugin source must name a registry package`
455</h3>
456
457A plugin whose marketplace entry uses an [`npm` source](/docs/en/plugins/marketplace-reference#npm-plugin-source) failed to install, update, or load, and the message includes this sentence. Claude Code checked the entry's `package` value before fetching anything and refused it. The message names the value and the reason:
458
459```text theme={null}
460"github:acme/formatter" was not installed: it is not an http or https link. An npm plugin source must name a registry package (name or name@version) or link to a tarball file. For a plugin in a git repository, use a "github", "url" or "git-subdir" source.
461```
462
463The marketplace's owner has to change the entry:
464
465* **If that's you**: change `package` to a value the [npm plugin source reference](/docs/en/plugins/marketplace-reference#npm-plugin-source) accepts, or switch the entry to a `github`, `url`, or `git-subdir` source
466* **If it isn't you**: report the message to the marketplace owner
467
453468<h3 id="marketplace-is-registered-from-an-untrusted-source">
454469 `Marketplace "<name>" is registered from an untrusted source`
455470</h3>
No line in this hunk matches that.