GitHits
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Security check for coding agents: malware, supply chain, secrets and web bugs. Reads, never runs.
목록은 사용 점수(100점 만점)로 정렬되며 구성은 다음과 같습니다
| 인기 | 6/80 | GitHub 별 또는 주간 다운로드: 큰 쪽 60, 작은 쪽 20 |
|---|---|---|
| 최신성 | 12/12 | 30일 안에 릴리스나 코드 변경이 있으면 만점 |
| 응답 중 | 0/8 | 마지막 점검 때 클라우드 엔드포인트가 응답 |
| 사용 점수 | 18/100 |
품질: 기본 점검 3/3개 통과(표시만, 정렬에는 안 씀) · 상승세: 데이터 없음 (급상승 탭에서만 사용)
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
검사 3/3 통과 · 내 컴퓨터에서 실행돼요
먼저: 어떤 AI를 쓰시나요?
쓰는 앱을 고르면 아래에 단계가 나옵니다.
Claude에 연결할 수 있지만 먼저 준비가 필요해요
키 필요 없음, 설치 필요 없음 · 컴퓨터용 Claude 앱(Windows 또는 Mac)에서만 되고 웹이나 모바일은 안 돼요
vetcode을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude가 vetcode을 쓰고 있다고 하거나 답에 vetcode 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
ChatGPT는 아직 vetcode에 연결할 수 없어요
vetcode는 내 컴퓨터에 설치해서 쓰지만 ChatGPT는 웹에서 도는 서버만 연결할 수 있어요
A · vetcode에 연결되는 앱 쓰기
B · 사이버 보안에서 ChatGPT에 연결되는 다른 서버
같은 분류에서 많이 쓰는 것 중 키 없이 주소만으로 연결되는 것을 골랐어요
Claude Code는 아직 vetcode에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · vetcode에 연결되는 앱 쓰기
Cursor는 아직 vetcode에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · vetcode에 연결되는 앱 쓰기
VS Code는 아직 vetcode에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · vetcode에 연결되는 앱 쓰기
이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.
내 컴퓨터에서 실행하는 앱
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 16일 점검
레지스트리 이름이 GitHub 계정 openyard-cloud 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
코드 마지막 변경: 3일 전
MIT 사용
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/servers/openyard-cloud-vetcode)질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.
아직 리뷰가 없어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 3일 전 변경됐고, 최신 버전(0.8.7)은 3일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 MCPB도 있어야 해요.
같은 카테고리에는: GitHits, Dependency Management MCP Server, Snyk MCP, Draugr, Spotdb
같은 카테고리, 다른 제작자, 명령 확인 완료. 공식이 먼저, 그다음 스타 순.
카드 보는 법:↓ 주간 다운로드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.
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
Ephemeral data sandbox for AI workflows with guardrails and security
| 이 항목 vetcode | GitHits | Dependency Management MCP Server | Snyk MCP | Draugr | Spotdb | |
|---|---|---|---|---|---|---|
| 실행 위치 | 컴퓨터에 설치 필요 | 클라우드 또는 컴퓨터 설치 모두 가능 | 클라우드에서 동작, 설치 불필요 | 컴퓨터에 설치 필요 | 컴퓨터에 설치 필요 | 컴퓨터에 설치 필요 |
| 키 필요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 |
| Claude에서 +로 추가 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 |
| 기본 점검 | 3/3 | 5/5 | 3/4 | 3/3 | 3/3 | 3/3 |
| 라이선스 | MIT | Apache-2.0 | – | Apache-2.0 | Apache-2.0 | MIT |
| 가격 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 |
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
vetcode
The security check your AI coding agent runs before it acts. Before it installs a package, after it clones a repository, before your code ships. Zero dependencies. Reads, never runs. Works without an agent too.
# Claude Code: the skill plus the guard that checks installs and clones
claude plugin marketplace add openyard-cloud/vetcode && claude plugin install vetcode@openyard
npx skills add openyard-cloud/vetcode # any other agent, as a skill npx github:openyard-cloud/vetcode#v0.8.7 . # no agent: scan a project, a package or a cloned repo
An agent installs a package in a second and runs a cloned project without reading it. vetcode is the check in between. It is three things:
| What it does | Where it runs | |
|---|---|---|
| The guard | Answers allow, ask or deny before a package is installed or an MCP server is added, and reads a repository right after it is cloned | Claude Code, on its own; other agents call it as a tool |
| The scanner | Reads a folder for malware, supply-chain attacks, attacks on agents, leaked secrets, and server and CI problems, and lists the places in web code worth reading | Skill, MCP server, command line, GitHub Action |
| The review procedure | Tells your agent how to confirm each finding by reading the code, and what to report | Skill, MCP server |
Nothing from the code it looks at is installed, built or run. It needs Node.js 18 or newer and nothing else. Free and open source (MIT), from the OpenYard community.
Contents: How good is it · Install · The guard · Use it · What it checks · How it works, and its limits
Every number here is measured, on samples the rules were not tuned on unless it says so. The scripts, the runs and the full history are in bench/.
| Question | vetcode | For comparison |
|---|---|---|
| Malicious npm packages caught, of 1,000 (false alarms on 1,000 clean ones) | 947 (26); verdicts 907 (5) | GuardDog: 903 (43) |
| Malicious PyPI packages caught, of 300 (false alarms on 210 clean ones) | 262 (16); verdicts 234 (1) | GuardDog: 241 (48) |
| The same malware after 8 kinds of disguise | still catches 99–100% of what it caught | GuardDog: 90–92% on several |
| Malicious agent skills it had never seen, of 157 (false alarms on 1,029 clean ones) | 91 (1) | Cisco skill-scanner: 101 (56) |
| The guard, shown malware as if nobody had reported it yet | blocks or questions 95% of npm, 88% of PyPI, and 3% of clean npm packages | |
| A package whose newest release is hours old, asked for 3 times | the agent installs the previous, settled version 3 times | the agent alone installs the new release 3 times |
| Wrong "this is malicious" verdicts on 72 real applications (228,000 files) | 1 | |
| Findings an agent has to read on those applications | about 4 per 1,000 files, plus 8 places to read | |
| Real injection bugs the scanner points at, of 480 advisories | 55 (11%); 6% on the half no rule was tuned on | |
| Real authorization bugs found by Claude Code with vetcode, of 49 advisories | 41% | Claude Code alone does as well |
A sign and a verdict are different things. A scanner of several hundred rules that lets any one of them call code malicious is wrong somewhere on almost every large project. vetcode reports every sign, which is what your agent is told to read, and gives a verdict, which is what stops an install without asking, only when a rule with a measured record fires, when two rules agree on one file, or when the sign sits in code an install script starts.
What it is good at. Malware and supply-chain attacks in packages and repositories, attacks aimed at coding agents (poisoned CLAUDE.md and skills, hooks and auto-approved MCP servers in project settings, tool descriptions that give orders), leaked secrets, and stepping in before the install, not after.
What it is not. It does not find web bugs by itself: it lists the dangerous calls as places to read, and those stand at about one real injection bug in ten, so they are where to start, not coverage. It does not make your agent better at logic bugs such as missing authorization; that is the agent's own ability. And a clean report means "nothing obvious found", not "safe".
Read the numbers with care. Samples are 157 to 1,000 items, so they move by a point or two between samples. Most malicious packages in the public datasets were found by GuardDog itself, which favours it. Cisco's scanner catches ten more skills by flagging 56 clean ones, a trade vetcode does not make. All numbers are the scanner alone; in normal use your agent reads every finding again.
All forms need Node.js 18+. vetcode is not on npm: every command here runs it from this repository, pinned to a release. A package called vetcode on npm or PyPI is not this project.
| Your agent | Use |
|---|---|
| Claude Code | the plugin (skill and guard), or the skill alone |
| Gemini CLI | the extension (skill, guard and MCP server) |
| Codex, GitHub Copilot, Cursor, Amp, Goose, opencode, Windsurf, Cline, Roo… | the skill |
| Anything that speaks MCP (Cursor, VS Code, Codex, Gemini CLI, Windsurf, Zed, Claude Desktop, ChatGPT…) | the MCP server |
| claude.ai | the skill zip |
| CI, scripts, or no agent at all | the command line or the GitHub Action |
claude plugin marketplace add openyard-cloud/vetcode && claude plugin install vetcode@openyard
Inside a session the same is two commands, because Claude Code only installs from marketplaces it already knows:
/plugin marketplace add openyard-cloud/vetcode
/plugin install vetcode@openyard
For a whole team
Commit this to the project's .claude/settings.json. Everyone who opens the project and trusts the folder gets the marketplace registered, so each person only runs /plugin install vetcode@openyard once:
{
"extraKnownMarketplaces": { "openyard": { "source": { "source": "github", "repo": "openyard-cloud/vetcode" } } }, "enabledPlugins": { "vetcode@openyard": true } }
The skill, the guard and the MCP server in one install:
gemini extensions install https://github.com/openyard-cloud/vetcode
Gemini CLI downloads the extension from the latest release. Its guard runs before every shell command and file write, like the Claude Code one, with one difference: Gemini CLI has no "ask" answer for a hook, so where Claude Code would ask, you see vetcode's warning and then Gemini CLI's own confirmation of the command. With auto-approval on (--yolo), set VETCODE_GUARD=strict to turn those warnings into a refusal.
For any agent that loads Agent Skills. The skills CLI knows where each agent keeps them (vetcode on skills.sh):
npx skills add openyard-cloud/vetcode
Or copy the folder yourself
git clone https://github.com/openyard-cloud/vetcode, then copy vetcode/skills/vetcode into your agent's skills folder, in the project or under your home folder: .agents/skills/ (shared by many agents, such as Codex and Copilot), .claude/skills/ (Claude Code), .github/skills/ (Copilot), .gemini/skills/ (Gemini CLI) or .cursor/skills/ (Cursor).
Four tools (vetcode_scan, vetcode_guard, vetcode_guide, vetcode_reference) and a security_review prompt. Most agents (.cursor/mcp.json, .mcp.json, Gemini CLI settings.json, Windsurf mcp_config.json):
{
"mcpServers": { "vetcode": { "command": "npx", "args": ["-y", "-p", "github:openyard-cloud/vetcode#v0.8.7", "vetcode-mcp"] } } }
Claude Desktop: download vetcode.mcpb from Releases and open it. The server is also in the MCP Registry as io.github.openyard-cloud/vetcode.
VS Code and Codex
VS Code (.vscode/mcp.json):
{ "servers": { "vetcode": { "type": "stdio", "command": "npx", "args": ["-y", "-p", "github:openyard-cloud/vetcode#v0.8.7", "vetcode-mcp"] } } }
Codex (~/.codex/config.toml):
[mcp_servers.vetcode]
command = "npx" args = ["-y", "-p", "github:openyard-cloud/vetcode#v0.8.7", "vetcode-mcp"]
Then ask your agent to "use vetcode to review this project". The agent should call vetcode_guide once; the server also tells it to.
Download vetcode-skill.zip from Releases and upload it under Settings → Capabilities → Skills.
For tools that read AGENTS.md (or .cursorrules, CONVENTIONS.md…) but neither skills nor MCP, clone this repository next to your project and add:
## Security reviews
When asked to check code for security problems or malware, follow ../vetcode/skills/vetcode/SKILL.md and run its scanner: node ../vetcode/skills/vetcode/scripts/vet.mjs .
An agent decides to install a package in a second: a name it remembered wrong, a name a web page suggested, a release published an hour ago. Installing runs that package's code with your rights. With the Claude Code plugin or the Gemini CLI extension, vetcode looks at every install command before it runs, and at every MCP server before it is registered, and answers allow, ask or deny:
| The command would… | Answer |
|---|---|
| install a package that does not exist (a made-up name is one an attacker can register) | deny |
| install a package with a malware advisory on OSV.dev | deny |
| install a package whose code gets a malware verdict at critical (the archive is downloaded and read, never run) | deny |
| install a package whose code shows signs of malware short of that | ask |
install a name one letter from a popular package (expres, reqeusts) that few people install | ask |
| install a release less than 72 hours old, or one that lost its provenance or gained an install script | ask |
| pipe a download into a shell, or install from another index, a repository or a URL | ask |
| add an MCP server at a tunnel address (ngrok, trycloudflare…) or over plain HTTP to another machine | ask |
| install well-known packages at settled versions | allow, silently |
"Ask" shows you the reason and waits fo