English Français العربية

io.github.flagrix-io/flagrix

Official registry Developer tools

Scan GitHub repos and profiles for malware before cloning — commit-pinned risk verdicts for agents

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package flagrix
Claude Code 
claude mcp add flagrix -e 'GITHUB_TOKEN=<your github_token>' -- npx -y flagrix@0.1.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "flagrix": {
            "command": "npx",
            "args": [
                "-y",
                "flagrix@0.1.0",
                "mcp"
            ],
            "env": {
                "GITHUB_TOKEN": "<your github_token>"
            }
        }
    }
}

Environment variables

  • GITHUB_TOKEN secret Optional GitHub token — raises API rate limits and enables private-repo scans

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. flagrix
  2. Commands
  3. Exit codes
  4. AI agents
  5. Tokens & rate limits
  6. Privacy
  7. How it works
  8. AI Disclosure
  9. License

flagrix

Scan GitHub repositories and profiles for malware before you clone — from the terminal, CI, or an AI agent. The same commit-pinned verdict as the Flagrix browser extension, made callable.

npx flagrix scan https://github.com/some-org/coding-assignment
  some-org/coding-assignment @ 3f9c2a1
  HIGH RISK — Do not clone  security score 12/100
  3 files scanned · 10 dependencies · 2 issues

  CRITICAL Data exfiltration patterns detected: Keylogger Pattern
    assignment.js:14
      14  document.addEventListener("keydown", (e) => send(e.key))

Built after real fake-recruiter campaigns ("coding assignment" repos that steal wallets, SSH keys, and browser sessions) started targeting developers.

Commands

flagrix scan <url | owner/repo>   # scan a repository (--ref <branch|sha>)
flagrix scan-user <username>      # score a GitHub profile for scam signals
flagrix mcp                       # MCP server (stdio) for AI agents

Exit codes

codemeaning
0low risk
1scan failed
2medium risk — review before proceeding
3high risk — do not clone

--json (automatic when stdout is piped) emits the full result. The verdict is pinned to the scanned commit (commitSha in the JSON): every file is read at that SHA, so a push mid-scan or after the verdict can't silently invalidate it.

AI agents

claude mcp add flagrix -- npx -y flagrix mcp

Tools: scan_github_repo, scan_github_user. A Claude Code hook that gates every git clone on a scan ships in hooks/ — see docs/agent-gating.md.

Tokens & rate limits

Unauthenticated scans use GitHub's 60 req/h budget (a scan issues one request per scanned file, up to ~50). Set GITHUB_TOKEN (or FLAGRIX_GITHUB_TOKEN, or --token) to raise it to 5,000/h and to scan private repositories.

Privacy

Fully local. No telemetry, no accounts, no Flagrix backend — the only network calls go to the GitHub/npm APIs and the public detection-rules repository (signature refresh, cached 6 h, with a bundled offline snapshot).

Dependencies are also checked against the OSV malicious-package feed (osv-malicious.json from the same repository: every npm/PyPI package the OpenSSF malicious-packages project has confirmed malicious). The feed is downloaded and matched locally, so dependency names never leave your machine. It is cached 6 h and revalidated with its ETag. Set FLAGRIX_OSV_FEED=0 to skip it (the curated list in the signatures still applies).

How it works

Scanning logic lives in @flagrix/scanner-core (MIT), signatures in flagrix-detection-rules (MIT) — the same engine and rules the browser extension uses. Verdicts are risk assessments, not definitive fraud determinations; always verify through official channels.

AI Disclosure

This project leverages Claude AI for boilerplate generation, test-suite expansion, and optimization. All AI-generated code is strictly reviewed, refactored, and verified by human maintainers before merging.

License

MIT — see LICENSE.

Frequently asked questions

What is io.github.flagrix-io/flagrix?

Scan GitHub repos and profiles for malware before cloning — commit-pinned risk verdicts for agents

How do I install io.github.flagrix-io/flagrix?

It runs on your machine. In Claude Code: claude mcp add flagrix -e 'GITHUB_TOKEN=<your github_token>' -- npx -y flagrix@0.1.0 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.flagrix-io/flagrix need an API key?

Yes. It expects GITHUB_TOKEN, which you set in its configuration.

Is io.github.flagrix-io/flagrix open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.flagrix-io/flagrix?

It is published by flagrix-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.