Audited 2026-10-18 · Sources: GitHub repo + README, Anthropic's own disclaimer text. Tabletop audit — nothing installed.
The card
| Repo | anthropics/claude-plugins-official |
| Stars | 42.8k (GitHub API, audit date) |
| License | Apache-2.0 |
| Born | November 2025 |
| What it is | Anthropic-managed directory of Claude Code plugins — installed via /plugin install <name>@claude-plugins-official |
What problem it solves
Provenance. Before this existed, "install a Claude Code plugin" meant finding a stranger's repo and hoping the username was who it claimed to be. An Anthropic-hosted directory answers the first question correctly every time: is this the real source.
Our gate findings — including Anthropic's own warning
This is the article where the label matters more than the verdict. Anthropic's README says, in their words:
"Make sure you trust a plugin before installing, updating, or using it. Anthropic does not control what MCP servers, files, or other software are included in plugins and cannot verify that they will work as intended or that they won't change."
Read that again. Official hosting is not vetting. Anthropic runs the front door — they do not inspect what each plugin does after install, what MCP servers it bundles, or what permissions it asks for. A plugin in the official directory is a known-source artifact, not a certified-safe artifact.
| Gate | Finding |
|---|---|
| Upstream identity | Verified — anthropics org, Apache-2.0 |
| Provenance | Strong — real source, no typosquat risk on the directory itself |
| Content safety | Per-plugin, unvetted. Each entry can bundle MCP servers, files, hooks — the same install-trust question as any third-party code, just with a trustworthy address |
| Immutable slugs | Plugin names can't be renamed post-publish (good — kills a bait-and-switch vector); the renames map handles migrations |
Verdict: CAUTION — treat the directory as a discovery source, not a trust mark. Trust the address, audit the package. Anthropic told you that themselves; we just underlined it.
Second-opinion reconciliation: our first pass scored this GO on provenance. An independent gate audit (Codex, 2026-10-19) argued CAUTION — the directory explicitly disclaims verification, so by our own stoplight rule every install still requires a per-plugin review. The second read wins: a directory you must re-audit anyway is a CAUTION, not a GO.
Best for
Anyone running Claude Code who wants extensions — this is now the right first place to look. Just keep the same install discipline you'd use anywhere else: read the plugin's files and MCP surface before enabling it.