Code Pathfinder

dev.codepathfinder由 codepathfinder.dev 发布v2.1.1更新于 Oct 24, 2026

Code intelligence MCP server: call graphs, type inference, and symbol search for Python/Go.

已验证STDIO仅桌面开发者工具安全与监控

概览

AI 生成的概览

一个本地代码智能 MCP 服务器,为助手提供 Python 与 Docker 项目的调用图、跨文件数据流追踪、符号搜索和安全规则扫描。

可以做什么
Code Pathfinder 将项目解析为 AST,构建调用图和每个函数的变量依赖图,并运行污点分析以追踪跨文件和跨函数边界的源到汇数据流。通过 MCP,它提供查找调用者与被调用者、追踪数据流、搜索代码模式以及运行安全规则的工具。它内置针对 Python、Dockerfile 和 Docker Compose 的规则包,并支持以文本、JSON、SARIF 或 CSV 输出结果。
适用场景
当助手需要超出 LSP 所能提供的 Python 代码结构理解时,或需要审查跨多个文件的 SQL 注入、SSRF、路径遍历、反序列化等漏洞时使用。它也适用于 Dockerfile 和 Compose 配置检查。
运行要求
以 stdio 方式作为本地进程运行。可通过 Homebrew、pip(codepathfinder)、预编译二进制或 Docker 镜像安装;pip 包还提供用于编写规则的 Python SDK。无需 API 密钥、配置文件或云账户。规则集会从 CDN 自动下载,因此需要网络访问。
安装前请注意
它会读取你指定的项目目录,因此请将其限定在你愿意暴露给助手的代码范围内。规则集从远程 CDN 获取,GitHub Action 中匿名使用指标默认开启(disable-metrics)。GitHub Action 可以发布拉取请求评论和内联审查评论,这需要 github-token。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Code Pathfinder,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Open-source SAST engine that traces vulnerabilities across files and functions

Website · Docs · Rule Registry · MCP Server · Blog

[Build] [GitHub Release] [Apache-2.0 License] [GitHub Stars] [Ask DeepWiki]


Quick Start

Install:

bash
brew install shivasurya/tap/pathfinder

Scan a Python project (rules download automatically):

bash
pathfinder scan --ruleset python/all --project .

Scan Dockerfiles:

bash
pathfinder scan --ruleset docker/all --project .

No config files, no API keys, no cloud accounts. Results in your terminal in seconds.


What is Code Pathfinder?

Code Pathfinder is an open-source static analysis engine that builds a graph of your codebase and traces how data flows through it. It parses source code into Abstract Syntax Trees, constructs call graphs across files, and runs taint analysis to find source-to-sink vulnerabilities that span multiple files and function boundaries.

v2.0 introduces cross-file dataflow analysis: trace user input from an HTTP handler in one file through helper functions and into a SQL query in another file. This is the kind of analysis that pattern-matching tools miss entirely.

Cross-File Taint Analysis

Most open-source SAST tools operate on single files. Code Pathfinder v2.0 tracks tainted data across file boundaries:

app.py:5    user_input = request.get("query")     ← Source: user-controlled input  ↓ callsdb.py:12    cursor.execute(query)                  ← Sink: SQL execution

The engine builds a Variable Dependency Graph (VDG) per function, then connects them through inter-procedural taint transfer summaries. When user_input flows into a function parameter in another file, the taint propagates through the call graph to the sink.

How It Works

Source Code → Tree-sitter AST → Call Graph → Variable Dependency Graph → Taint Analysis → Findings                                     ↓                              Inter-procedural                              Taint Summaries                              (cross-file flows)
  1. Parse: Tree-sitter builds ASTs for Python, Dockerfiles, and Docker Compose files
  2. Index: Extract functions, call sites, parameters, and assignments into a queryable call graph
  3. Analyze: Build VDGs per function, resolve inter-procedural flows, run taint analysis
  4. Detect: Python-based security rules query the graph to find source-to-sink paths
  5. Report: Output findings as text, JSON, SARIF (GitHub Code Scanning), or CSV

190 Security Rules, Ready to Use

Rules download from CDN automatically. No need to clone the repo or manage rule files.

LanguageBundlesRulesCoverage
Pythondjango, flask, aws_lambda, cryptography, jwt, lang, deserialization, pyramid158SQL injection, RCE, SSRF, path traversal, XSS, deserialization, crypto misuse, JWT vulnerabilities
Dockersecurity, best-practice, performance37Root user, exposed secrets, image pinning, multi-stage builds, layer optimization
Docker Composesecurity, networking10Privileged mode, socket exposure, capability escalation, network isolation
bash
# Scan with a specific bundlepathfinder scan --ruleset python/django --project .
# Scan with multiple bundlespathfinder scan --ruleset python/flask --ruleset python/jwt --project .
# Scan a single rulepathfinder scan --ruleset python/PYTHON-DJANGO-SEC-001 --project .
# Scan all rules for a languagepathfinder scan --ruleset python/all --project .

Browse all rules with examples and test cases at the Rule Registry.

MCP Server for AI Coding Assistants

Code Pathfinder runs as an MCP server, giving Claude Code, Cursor, Cline, and other AI assistants access to call graphs, data flows, and security analysis. More context than LSP, focused on security and code structure.

bash
pathfinder serve --project .

The MCP server exposes tools for querying the code graph: find callers/callees, trace data flows, search for patterns, and run security rules — all available to the AI assistant during code review or development.

Write Custom Rules

Security rules are Python scripts using the PathFinder SDK. Define sources, sinks, and sanitizers — the dataflow engine handles the analysis.

Here's a real rule from the repo (PYTHON-DJANGO-SEC-001) that detects SQL injection in Django:

python
from codepathfinder import calls, flows, QueryTypefrom codepathfinder.presets import PropagationPresets
class DBCursor(QueryType):    fqns = ["sqlite3.Cursor", "psycopg2.extensions.cursor"]    match_subclasses = True
@python_rule(    id="PYTHON-DJANGO-SEC-001",    name="Django SQL Injection via cursor.execute()",    severity="CRITICAL",    cwe="CWE-89",)def detect_django_cursor_sqli():    return flows(        from_sources=[            calls("request.GET.get"),            calls("request.POST.get"),        ],        to_sinks=[            DBCursor.method("execute").tracks(0),            calls("cursor.execute"),        ],        sanitized_by=[calls("escape"), calls("escape_string")],        propagates_through=PropagationPresets.standard(),        scope="global",  # cross-file taint analysis    )
bash
# Run your custom rulespathfinder scan --rules ./my_rules/ --project .

Explore all 190 rules in the rules/ directory or browse the Rule Registry. See the rule writing guide and dataflow documentation to write your own.

See the rule writing guide and dataflow documentation for more.

Installation

Homebrew (Recommended)

bash
brew install shivasurya/tap/pathfinder

pip

Installs the CLI binary and Python SDK for writing rules.

bash
pip install codepathfinder

Docker

bash
docker pull shivasurya/code-pathfinder:stable-latest
docker run --rm -v "$(pwd):/src" \  shivasurya/code-pathfinder:stable-latest \  scan --ruleset python/all --project /src

Pre-Built Binaries

Download from GitHub Releases for Linux (amd64, arm64), macOS (Intel, Apple Silicon), and Windows (x64).

From Source

bash
git clone https://github.com/shivasurya/code-pathfindercd code-pathfinder/sast-enginegradle buildGo./build/go/pathfinder --help

Usage

bash
# Scan with text output (default)pathfinder scan --ruleset python/all --project .
# JSON outputpathfinder scan --ruleset python/all --project . --output json --output-file results.json
# SARIF output (GitHub Code Scanning)pathfinder scan --ruleset python/all --project . --output sarif --output-file results.sarif
# CSV outputpathfinder scan --ruleset python/all --project . --output csv --output-file results.csv
# Fail CI on critical/high findingspathfinder scan --ruleset python/all --project . --fail-on=critical,high
# MCP server modepathfinder serve --project .
# Verbose output with statisticspathfinder scan --ruleset python/all --project . --verbose

GitHub Action

yaml
name: Code Pathfinder Security SAST Scan
on:  pull_request:
permissions:  security-events: write  contents: read  pull-requests: write
jobs:  security-scan:    runs-on: ubuntu-latest    steps:      - uses: actions/checkout@v6        with:          fetch-depth: 0
      - name: Run Security Scan        uses: shivasurya/[email protected]        with:          ruleset: python/all, docker/all, docker-compose/all          verbose: true          pr-comment: ${{ github.event_name == 'pull_request' }}          pr-inline: ${{ github.event_name == 'pull_request' }}          github-token: ${{ secrets.GITHUB_TOKEN }}
      - name: Upload SARIF        uses: github/codeql-action/upload-sarif@v4        if: always()        with:          sarif_file: pathfinder-results.sarif

See the full example: .github/workflows/code-pathfinder-scan.yml

Action Inputs
InputDescriptionDefault
rulesPath to local Python rule files or directory-
rulesetRemote ruleset(s), comma-separated (e.g., python/all, docker/security)-
projectPath to source code.
outputOutput format: sarif, json, or csvsarif
output-fileOutput file pathpathfinder-results.sarif
fail-onFail on severities (e.g., critical,high)-
verboseEnable verbose outputfalse
debugEnable debug diagnostics with timestampsfalse
skip-testsSkip test filestrue
refresh-rulesForce refresh cached rulesetsfalse
disable-metricsDisable anonymous usage metricsfalse
python-versionPython version to use3.12
pr-commentPost summary comment on pull requestfalse
pr-inlinePost inline review comments for critical/high findingsfalse
github-tokenGitHub token (required when pr-comment or pr-inline is enabled)-
no-diffDisable diff-aware scanning (scan all files)false

Either rules or ruleset is required.

Supported Languages

LanguageAnalysisStatus
PythonCross-file dataflow, taint analysis, call graphsStable
DockerfileInstruction analysis, security patternsStable
Docker ComposeConfiguration analysis, security patternsStable
GoAST analysis, call graphsComing soon

Contributing

Contributions are welcome. Read the Contributing Guide for setup instructions, how to run tests locally, and the PR process.

Pushing an in-product announcement

In-product announcements (workshops, blog posts, security advisories) are managed via release/latest.json. Add an entry to announcements[], open a PR, and once it merges to main the publish workflow uploads the manifest to the CDN within ~60 seconds. See the version-update-check tech spec for the schema and version_range semantics.

All contributors must sign the Contributor License Agreement (CLA) before any pull request can be merged.

License

Apache-2.0

来源:README.md,提交 460d0d3

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v2.1.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分