GitHits
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Scans AI-written code for leaked secrets, unguarded routes and missing RLS.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 29/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 41/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 70 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 vibe-shield — security scanner for AI-generated code。按照 https://mcp.popnx.com/i/avivgerz-hue-vibe-shield.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月17日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server vibe-shield — security scanner for AI-generated code,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "vibe-shield": { "command": "npx", "args": [ "-y", "@vibefoundry/vibe-shield", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 vibe-shield — security scanner for AI-generated code 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"vibe-shield": {
"command": "npx",
"args": [
"-y",
"@vibefoundry/vibe-shield",
"mcp"
]
}
}
}用 vibe-shield — security scanner for AI-generated code 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 vibe-shield — security scanner for AI-generated code,或回答中出现 vibe-shield — security scanner for AI-generated code 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 vibe-shield — security scanner for AI-generated code
vibe-shield — security scanner for AI-generated code 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 vibe-shield — security scanner for AI-generated code 的应用
B · 网络安全 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server vibe-shield — security scanner for AI-generated code,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user vibe-shield -- npx -y @vibefoundry/vibe-shield mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 vibe-shield — security scanner for AI-generated code 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user vibe-shield -- npx -y @vibefoundry/vibe-shield mcp应能看到 vibe-shield — security scanner for AI-generated code 在列表中并显示已连接
用 vibe-shield — security scanner for AI-generated code 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 vibe-shield — security scanner for AI-generated code,或回答中出现 vibe-shield — security scanner for AI-generated code 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server vibe-shield — security scanner for AI-generated code,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "vibe-shield": { "command": "npx", "args": [ "-y", "@vibefoundry/vibe-shield", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 vibe-shield — security scanner for AI-generated code 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 vibe-shield — security scanner for AI-generated code 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 vibe-shield — security scanner for AI-generated code,或回答中出现 vibe-shield — security scanner for AI-generated code 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server vibe-shield — security scanner for AI-generated code,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "vibe-shield": { "type": "stdio", "command": "npx", "args": [ "-y", "@vibefoundry/vibe-shield", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 vibe-shield — security scanner for AI-generated code 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 vibe-shield — security scanner for AI-generated code 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 vibe-shield — security scanner for AI-generated code,或回答中出现 vibe-shield — security scanner for AI-generated code 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user vibe-shield -- npx -y @vibefoundry/vibe-shield mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"vibe-shield": {
"command": "npx",
"args": [
"-y",
"@vibefoundry/vibe-shield",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"vibe-shield": {
"command": "npx",
"args": [
"-y",
"@vibefoundry/vibe-shield",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"vibe-shield": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vibefoundry/vibe-shield",
"mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 avivgerz-hue 验证,该账户拥有此仓库
代码最后更新于3天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/avivgerz-hue-vibe-shield)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于3天前,最新版本(2.1.3)于3天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:GitHits, Dependency Management MCP Server, Snyk MCP, TokenSafe, Draugr
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Sonatype component intelligence: versions, security analysis, and Trust Score recommendations
Easily find and fix security issues in your applications leveraging Snyk platform capabilities.
Your AI agent is smart enough to code all day. Local firewall & zero-loss runtime.
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
| 本项 vibe-shield — security scanner for AI-generated code | GitHits | Dependency Management MCP Server | Snyk MCP | TokenSafe | Draugr | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 需要安装在电脑上 | 云端或安装在电脑上都可以 | 需要安装在电脑上 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 5/5 | 3/4 | 3/3 | 5/5 | 3/3 |
| 许可证 | MIT | Apache-2.0 | – | Apache-2.0 | MIT | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The security gate for AI-written code. Find exposed secrets, unguarded routes and missing RLS before you ship.
⭐ If this tool helps your AI coding workflow, please give this repository a Star! It helps more developers discover the project.
npx -y @vibefoundry/vibe-shield@latest scan .
Illustrative two-file scan; fixes are applied manually. Results vary by project. A clean score is not a security guarantee.
npx -y unslop-mcp@latest initnpx -y @vibefoundry/vibe-shield@latest scan .npx -y ghost-qa@latest test http://localhost:3000vibe-shield is a static security scanner plus an Agent Skill that helps Claude Code, Codex, Cursor and Windsurf audit before they say *“done”*.
The v2 catalogue covers client exposure; auth and route protection; database/RLS; AI and web sinks; infrastructure; dependency hygiene; secrets and cryptography; and agent/MCP integrity. The new hardening checks include production source maps, insecure JWT settings, explicit and omitted cookie flags, locally absent security headers, container users, lifecycle scripts, lockfiles and weak cryptography. Run rules for the complete catalogue.
The scanner produces a heuristic attack-surface inventory of route methods, observed guard signals, SQL tables and RLS signals, AI entrypoints, and MCP/agent files. Header checks cover recognized server configuration files; cookie checks cover common literal setter options. Both are advisory: external middleware, deployment settings and dynamic options require review. Signals do not prove guards or policies work, and code outside the scanned scope is not assessed. Run audit-skills separately for agent-integrity checks.
Generate an executive report or agent remediation prompt explicitly:
npx -y @vibefoundry/vibe-shield scan --report SECURITY-REPORT.md --patch-prompt PATCH-PROMPT.md
npx -y @vibefoundry/vibe-shield scan --format html --out security-report.html npx -y @vibefoundry/vibe-shield audit-skills --report agent-report.html
Reports include severity, CWE, locations, snippets, OWASP 2025 web mappings for every rule and contextual LLM mappings when applicable, and illustrative remediation. Examples are not automatic project-specific patches; validate them against the application. The scanner itself is offline and read-only by default; --cache, --out, --report, --patch-prompt and init explicitly write files. Installing with npx can require network access. An A+ score applies only to the rules and files examined and is not a security certification.
The npm
2.0.0artifact predates the universal--agentsinitializer. Use npm2.1.0or later (once published), or the GitHubv2ref. To exercise this checkout locally, runnpm ci && npm run build, thennode dist/bin/vibe-shield.jswith the same arguments.
This is the shape of code an agent writes when you ask for "a delete endpoint":
// app/api/users/route.ts
export async function DELETE(req: Request) { const { id, userId } = await req.json(); await db.query(DELETE FROM users WHERE id = ${id} AND owner = ${userId}); return new Response('ok'); }
It works. It also has three critical vulnerabilities — no authentication, SQL injection, and an IDOR that lets the caller choose whose data they delete. Nothing in a normal review loop catches all three, and the agent reported the task as complete.
npx -y @vibefoundry/vibe-shield scan catches all three in 17 milliseconds:
🛡️ vibe-shield · security scan (illustrative output for current source)
target /home/you/app
💀 GRADE F — 0/100 · 3 critical
CRITICAL 3 ███
Findings
app/api/users/route.ts CRITICAL 2:1 VSB-AUTH-001 Next.js App Router mutation handler has no authentication check export async function DELETE(req: Request) { CRITICAL 4:22 VSB-DB-007 SQL statement built by concatenating request data await db.query(DELETE FROM users WHERE id = ${id} AND owner = ${userId}); CRITICAL 4:22 VSB-AUTH-004 Record ownership taken from the request instead of the session (IDOR)
7 files · 1 KiB · 412 files/s · 17 ms · 80 rules
⚠ 3 critical findings — rotate any exposed credential before anything else. Fix it npx -y @vibefoundry/vibe-shield scan --fix-prompt # writes SECURITY_PATCH_PROMPT.md for your agent Explain npx -y @vibefoundry/vibe-shield explain VSB-AUTH-001 Gate CI npx -y @vibefoundry/vibe-shield scan --fail-on critical --format github
Then hand the fix list to the agent that wrote the bug:
npx -y @vibefoundry/vibe-shield scan --fix-prompt # → SECURITY_PATCH_PROMPT.md
That file contains, for every finding: the severity, the CWE id and link, the exact file:line, the vulnerable snippet, the ordered remediation steps, the target code shape, and a verification command. It is written for a machine to execute and a human to audit.
# 1. Scan (npx may download the package; the scanner itself is offline)
npx -y @vibefoundry/vibe-shield scan
npx -y @vibefoundry/vibe-shield scan --fix-prompt
npx -y github:avivgerz-hue/vibe-shield#v2 init --agents all
Use the scoped name. vibe-shield is published as
The *unscoped* name
vibe-shieldon npm belongs to an unrelated project, so
npx vibe-shieldruns someone else's code. Always include the@vibefoundry/
scope. The package ships a prebuilt
dist/, needs no TypeScript, and
starts in milliseconds.
Run this from the repository you want to protect (Node.js and Git required):
npx -y github:avivgerz-hue/vibe-shield#v2 init --agents all
To configure selected agents, substitute a comma-separated list such as --agents claude,cursor,zed:
| Agent | Selector | Native integration |
|---|---|---|
| Claude Code | claude | .mcp.json, CLAUDE.md, .claude/skills/vibe-shield/SKILL.md, .claude-plugin/plugin.json |
| OpenCode | opencode | opencode.json MCP and AGENTS.md |
| OpenAI Codex CLI / universal agents | codex | AGENTS.md and .agents/skills/vibe-shield/SKILL.md |
| Cursor | cursor | .cursor/mcp.json and .cursor/rules/vibe-shield.mdc |
| Windsurf | windsurf | .windsurfrules |
| VS Code / GitHub Copilot | copilot | .vscode/mcp.json and .github/copilot-instructions.md |
| Cline / Roo Code | cline or roo | .clinerules |
| Zed | zed | .zed/settings.json context server |
The existing --agent claude|cursor|generic|all remains supported. The shared .mcp.json, ignore file, and (unless --no-workflow is set) CI workflow are also installed. JSON configuration is merged by server name; malformed JSON or JSON with comments is left untouched and reported. Existing instructions are appended only once, and existing files are not overwritten without --force. Restart the relevant editor or reload its configuration after setup.
Traditional SAST rules are built around human mistakes: a forgotten escape, a missing prepare(). Agent-written code fails differently — it is *confidently complete* and *structurally plausible*:
| What a human does | What an agent does |
|---|---|
| forgets to validate one input | writes a perfect endpoint with no auth at all |
uses eval in one legacy file | puts a tool `execute` that shells out behind an LLM |
commits a .env by accident | puts SUPABASE_SERVICE_ROLE_KEY behind NEXT_PUBLIC_ because "it needed the env var" |
writes CREATE TABLE | writes CREATE TABLE and forgets the `ENABLE ROW LEVEL SECURITY`, so the anon key reads everything |
adds dangerouslySetInnerHTML to render a doc | renders model output with it, creating stored XSS with a step counter |
vibe-shield encodes those specific shapes: 92 signatures across eight defensive categories, each one derived from a real agent-generated bug rather than a generic CWE checklist.
Client-boundary limitation: Client reachability is a best-effort static graph of literal imports, re-exports and require calls using relative paths and root tsconfig.json/jsconfig.json aliases. Dynamic paths, inherited or nested configurations, excluded or oversized files and other bundler resolution may be missed. A server-side service-role helper still bypasses RLS: use import 'server-only', authorize every privileged request, and verify the production bundle. Auth-helper names and with* wrappers are signals, not proof that authorization is enforced.
80 code signatures + 12 agent-integrity signatures = 92. The scan command runs the 80 code rules; audit-skills runs the 12 agent rules. Every rule has an id, a CWE, an illustrative vulnerable shape, remediation guidance, and an OWASP association — run npx -y @vibefoundry/vibe-shield rules or npx -y @vibefoundry/vibe-shield explain .
VSB-CLIENT-*| ID | Detects | CWE | Sev |
|---|---|---|---|
VSB-CLIENT-001 | NEXT_PUBLIC_ / VITE_ / PUBLIC_ / REACT_APP_ + a server-only secret name (SERVICE_ROLE_KEY, OPENAI_API_KEY, STRIPE_SECRET_KEY, DATABASE_URL…) | CWE-200 | critical |
VSB-CLIENT-002 | server-only process.env.*SECRET* read inside a "use client" module | CWE-200 | high |
VSB-CLIENT-003 | createClient(url, SERVICE_ROLE_KEY) — RLS bypass in a client-reachable file or public env | CWE-250 | critical |
VSB-CLIENT-004 | supabaseAdmin / adminClient / serviceRoleClient referenced from browser code | CWE-250 | critical |
VSB-CLIENT-005 | dangerouslyAllowBrowser: true, provider SDK keyed in the browser | CWE-749 | high |
VSB-CLIENT-006 | .env* assigns a live-looking credential to a public variable | CWE-540 | critical |
VSB-CLIENT-007 | next.config.js env / publicRuntimeConfig / Vite define inlining a secret | CWE-798 | critical |
VSB-AUTH-*| ID | Detects |