| FMRS | 49 / 100 · D | 76 / 100 · B |
|---|
| Reliability | 8 / 20 | 13 / 20 |
|---|
| Security and permissions | 10 / 20 | 14 / 20 |
|---|
| Maintenance | 8 / 20 | 18 / 20 |
|---|
| Documentation | 12 / 20 | 17 / 20 |
|---|
| Setup experience | 11 / 20 | 14 / 20 |
|---|
| Best for | - Developers using Claude Code, Cursor, Windsurf, Cline, OpenCode, or another supported AI coding client
- Teams reviewing AI-generated code, MCP tools, prompts, and supply-chain risks
- Teams needing security evidence before CI, releases, or vendor reviews
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - Users who only need traditional dependency vulnerability scanning
- Users looking for a replacement for npm audit
- Users needing hosted semantic review without configuring a model provider
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - Read access to projects, files, Git diffs, MCP servers, or dependency data being scanned
- The auto-fix capability may require write access to project files
- Semantic review uses the model provider selected by the user
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - AI-generated code may introduce SQL injection, XSS, command injection, unsafe cryptography, or secrets
- MCP tools may contain description injection, tool-name spoofing, environment-variable exposure, or command-execution risks
- AI-generated package names may not exist, creating package-squatting or dependency-confusion risks
- Semantic review sends relevant content to the selected provider; rule-based scans and MCP scans run locally
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Code, Cursor, Claude Desktop, Windsurf, Cline, Kilo Code, OpenCode, Cody | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp |
|---|
| Tools | 17 | 15 |
|---|