Code Pathfinder

dev.codepathfinderPublished by codepathfinder.devv2.1.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local code-intelligence MCP server that gives assistants call graphs, cross-file dataflow tracing, symbol search, and security rule scanning for Python and…

What you can do
Code Pathfinder parses a project into an AST, builds a call graph and per-function variable dependency graphs, and runs taint analysis to trace source-to-sink flows across files and function boundaries. Through MCP it exposes tools to find callers and callees, trace data flows, search for code patterns, and run security rules. It ships with rule bundles for Python, Dockerfiles, and Docker Compose, and reports findings as text, JSON, SARIF, or CSV.
When to use it
Use it when an assistant needs structural understanding of a Python codebase beyond what an LSP provides, or when reviewing code for vulnerabilities such as SQL injection, SSRF, path traversal, and deserialization that span multiple files. It is also useful for Dockerfile and Compose configuration checks.
Requirements
Runs as a local process over stdio. Install via Homebrew, pip (codepathfinder), a prebuilt binary, or the Docker image; the pip package also provides the Python SDK for writing rules. No API keys, config files, or cloud accounts are needed. Rulesets download from a CDN automatically, so network access is required for those.
Before you install
It reads the project directory you point it at, so scope it to code you intend to expose to the assistant. Rulesets are fetched from a remote CDN, and anonymous usage metrics are enabled by default in the GitHub Action (disable-metrics). The GitHub Action can post pull-request comments and inline review comments, which requires a github-token.

Installation

In SourceWeft

  1. Open Code Pathfinder in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Source: README.md at commit 460d0d3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts