Market statistics市场统计
Computed from the published index由已发布的索引计算 · index.json · source
Coverage覆盖率
Each row counts its own subset. Where upstream publishes nothing, the entry is unmeasured — not zero.每一行统计的是各自的子集。上游没有提供的数据是「未测量」,不是 0。
-
Has a star count有星标数 6,353/ 6,39099%
Upstream publishes a star count for these; the rest are unmeasured, not zero.上游为这些条目提供了星标数;其余是「未测量」,不是 0。
-
Has a download count有下载量 3,426/ 6,39054%
npm download counts, where the registry reports one.npm 下载量,仅包含 registry 会报告的那些。
-
Lists a version history列出了版本历史 2,875/ 6,39045%
More than one installable version. The rest are git-pinned entries or packages with a single release.拥有一个以上可安装版本。其余是固定提交的 git 条目或只发过一版的包。
-
Declares engines.dsh声明了 engines.dsh 1,064/ 6,39017%
A version states which DSH versions it runs on. The rest are checked only at install time.某个版本声明了它支持的 DSH 版本范围。其余只能在安装时检查。
-
Has a category有分类 6,390/ 6,390100%
Category ids come from the upstream catalog and are declared in this index.分类 id 来自上游目录,并在本索引中声明。
-
Carries a label带有标签 3,444/ 6,39054%
At least one capability, risk, or popularity label — the filterable vocabulary.至少一个能力、风险或热度标签——即筛选用的词表。
-
Has a risk finding带有风险标记 416/ 6,3907%
Upstream's trust scan flagged something: credentials with network, install-time code, plaintext http, or a bare IP.上游信任扫描发现了问题:凭据配合联网、安装时执行代码、明文 http,或直连 IP。
Versions per plugin每个插件的版本数
The market keeps the most recent five versions per plugin, plus the highest version and the highest stable one.市场为每个插件保留最近的五个版本,外加最高版本与最高稳定版。
- 1 version1 个版本 3,515
- 2–3 versions2–3 个版本 745
- 4–5 versions4–5 个版本 2,109
- 6 or more6 个及以上 21
Plugins per category各分类的插件数
- UI EnhancementsUI 增强 1,198
- Tools工具 850
- Sessions & Messages会话与消息 441
- Development开发 416
- Workflow工作流 370
- Models & Providers模型与账号接入 349
- Usage & Billing用量与计费 338
- Memory记忆 267
- Themes & Appearance主题与外观 252
- Skills技能 242
- Notifications通知 234
- Fun娱乐 199
- Security安全 191
- Remote远程 189
- Browser浏览器 140
- GitGit 138
- Vision视觉 128
- Documents文档 99
- Marketplace插件市场 93
- Voice语音 85
- WSLWSL 80
- Identity & Communication身份与通信 55
- AGI Architecture ExplorationAGI 架构探索 36
Plugins per label各标签的插件数
Labels are the filterable vocabulary: capabilities, risk findings, and popularity buckets.标签即筛选词表:能力、风险发现与热度分档。
- Reads files读取文件 2,359
- Network access访问网络 1,953
- Writes files写入文件 1,900
- Reads environment读取环境变量 1,886
- ★ 1+ stars★ 1+ 星标 1,863
- ⤓ 1k+ downloads⤓ 1k+ 下载 1,822
- ⤓ 100+ downloads⤓ 100+ 下载 1,358
- Runs shell commands执行 Shell 命令 1,246
- ★ No stars yet★ 暂无星标 852
- ★ 10+ stars★ 10+ 星标 550
- Touches credentials涉及凭据 413
- ⚠ Reads secrets and has network⚠ 读取密钥且联网 336
- Calls an LLM调用 LLM 316
- Accesses host runtime访问宿主运行时 294
- Generates code at runtime运行时生成代码 197
- ⤓ Few downloads⤓ 少量下载 143
- ★ 100+ stars★ 100+ 星标 125
- ⤓ 10k+ downloads⤓ 1 万+ 下载 101
- Spawns subagents创建子智能体 78
- ⚠ Uses plaintext http⚠ 使用明文 http 66
- ★ 1k+ stars★ 1k+ 星标 36
- ⚠ Contacts a bare IP address⚠ 直连 IP 地址 31
- ⚠ Runs code on install⚠ 安装时执行代码 18
- ⤓ No downloads yet⤓ 暂无下载 2
Who uses this index谁在使用这份索引
Mentioning a project and using it are different things, so each entry is graded. “Reads the JSON” means the published index URL appears in that repository, so something there can load it. “Mentions only” means just the name appears. A fork can publish a copy of its own.「提到」与「使用」是两件事,因此每条都标了档位。「读取了 JSON」表示该仓库里出现了已发布的索引地址,说明那里的东西能加载它;「仅提及」表示只出现了项目名;fork 则可能自行发布一份副本。
No users found, but the sweep did not complete — so this says nothing about whether any exist.未发现使用方,但本次扫描并未完成——因此这不能说明是否真的没有。
A market can be used without leaving a public trace: a client adds the index URL in Discover and nothing is published. When every entry is the weak tier, that is the expected picture rather than a contradiction — it means the market is being linked to but no public code points at it yet.市场被使用可以不留下公开痕迹:客户端在 Discover 里填入索引地址即可,什么都不会被发布出去。当所有条目都处于较弱的档位时,这是正常的,并非矛盾——它说明这份市场被链接到了,但还没有公开代码指向它。
The code search index does not cover every repository or every recent change — this project cannot find its own files with it — so these are floors, not totals. And GitHub Pages keeps no access log, so how many clients actually loaded the index is recorded nowhere.代码搜索对小型与刚更新的仓库索引并不完整——本项目自己的文件也无法被完整搜到——因此这些是下限而非总数。另外 GitHub Pages 不保留访问日志,所以究竟有多少客户端真的加载过索引,没有任何地方记录。
- 0 forks of this repository — each can publish its own copy of the index个本仓库的 fork——每一个都可以自行发布一份索引副本