Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Marketplace Security: Safe-to-Run verification benchmark for curated MCP servers & plugins

已关闭
#6,347 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
18/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
shell
领域
security

调研方向

This issue is a third-party pitch for an external Safe-to-Run audit URL, not a scoped change in the marketplace repo. There are no files, tests, or badge specs named. Start by reading the marketplace contribution and plugin-curation docs in this repository and any existing security or listing policy. Done would mean maintainers deciding whether to adopt an audit process and documenting that policy—not implementing the linked engine.

由索引模型根据 Issue 内容生成。

描述

needs-human needs-triage

Safe-to-Run Security Verification for Curated MCP Plugins

Hello melodic-software team,

As a marketplace aggregating community skills, hooks, and MCP servers for Claude Code, verifying the safety profile of contributed plugins is critical for user trust.

Developers installing third-party MCP servers onto their local machines risk exposing host filesystems, shell execution surfaces, and credential stores.

We built an automated Safe-to-Run Assessment Engine that verifies:

  1. Filesystem Confinement: Checks whether file tools enforce workspace boundary jailing.
  2. Command Injection Risks: Detects unparameterized shell concatenation.
  3. Secret Redaction: Confirms that API keys and environment secrets are not leaked in tool responses.
  4. Action Safety: Flags ungated destructive mutations.

You can run automated safety audits on candidate plugins at:
👉 GENESIS Safe-to-Run Verification Engine

We would be glad to offer this automated assessment framework to help establish verification badges for marketplace submissions!

主要语言
Shell
星标
22
派生
2
平均合并
8 小时 44 分钟
30 天内合并 PR
926

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

melodic-software/claude-code-plugins 的其他 Issue

查看 melodic-software/claude-code-plugins 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。