Flagrix

io.github.flagrix-io由 GitHub 帳號 flagrix-io 發布v0.1.0更新於 Oct 24, 2026

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

已驗證STDIO僅桌面開發者工具安全與監控

概覽

AI 產生的概覽

Flagrix 掃描 GitHub 儲存庫與使用者個人檔案中的惡意軟體和詐騙訊號,在複製程式碼前為助理提供綁定特定提交的風險判定。

可以做什麼
依 URL 或 owner/repo 掃描 GitHub 儲存庫,可指定分支或提交,回傳綁定所掃描提交的風險判定,包含安全分數、掃描檔案數、相依套件與問題清單。為 GitHub 使用者個人檔案評分詐騙訊號。以 JSON 回傳完整結構化結果,供助理解讀。
適用情境
適合在助理被要求複製、審查或執行陌生程式碼時使用,尤其是透過招募邀約、程式作業或不明連結送來的儲存庫,先做風險檢查。也適合在信任某個 GitHub 帳號的儲存庫之前先查核該帳號。
執行需求
透過 npx 在本機執行,需要 Node.js。需要存取 GitHub 與 npm API,以及一個公開的偵測規則儲存庫。選用的 GITHUB_TOKEN(或 FLAGRIX_GITHUB_TOKEN)可提高速率限制並支援掃描私有儲存庫;未設定時掃描共用 GitHub 未驗證請求額度。
安裝前請注意
判定結果是風險評估,並非確定的詐騙結論,應透過官方管道查證。GITHUB_TOKEN 權限較大,應盡量縮小範圍。掃描會透過 GitHub API 讀取儲存庫內容,簽章更新會連線到第三方規則儲存庫。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Flagrix,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

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.

bash
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

bash
flagrix scan <url | owner/repo>   # scan a repository (--ref <branch|sha>)flagrix scan-user <username>      # score a GitHub profile for scam signalsflagrix 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

bash
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.

來源:README.md,提交 79c5ed1

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分