BlastTrace
Pre-Edit Full-Stack Breaking-Change & Contract Blast-Radius Engine
Database$\leftrightarrow$Backend ORM$\leftrightarrow$API Route$\leftrightarrow$Frontend UI$\leftrightarrow$Tests
⚡ What is BlastTrace?
BlastTrace is a high-performance Model Context Protocol (MCP) server and standalone CLI that prevents AI coding agents (and human developers) from silently breaking full-stack web applications.
Existing AST tools only trace single-language file imports (File A -> File B). They go 100% blind when a schema edit crosses boundaries:
[Database Column: users.billing_balance]
↓
[Backend ORM Model: User.billing_balance]
↓
[API Endpoint: GET /api/v1/user/summary]
↓
[Frontend UI Component: CheckoutModal.tsx (data.billing_balance)]
↓
[Unit & E2E Tests: test_checkout.py, checkout.spec.ts]
BlastTrace deterministically bridges this gap using the BlastTrace Native Core, catching breaking changes before the file is saved, before git commit, and before pull requests merge.
🚀 Quick Start
1. Installation
pip install blasttrace
Or run zero-install via uvx:
uvx blasttrace
2. Standalone CLI Usage (Zero AI Required)
# Check if a proposed edit or signature change breaks downstream consumers
blasttrace check src/api/routes.py --symbol get_user_profile
# Inspect current git diff for breaking full-stack changes
blasttrace diff
# Install git pre-commit safety gate across your repo
blasttrace pre-commit --install
3. Connect to AI Agents & IDEs (Cursor, Claude Code, Windsurf, VS Code)
Add to your claude_desktop_config.json or .cursor/mcp.json:
{
"mcpServers": {
"blasttrace": {
"command": "blasttrace"
}
}
}
🛡️ Supported Technology Stacks
- Database & Schemas: PostgreSQL, MySQL, SQLite migrations (
.sql), Prisma (schema.prisma), Drizzle ORM, SQLAlchemy & Django ORM (models.py). - Backend & APIs: Python (FastAPI, Flask, Django REST, async functions, classes), Node.js / TypeScript (Express, Next.js App Router
app/api/.../route.ts, NestJS, OpenAPI / Swagger specs). - Frontend Consumers: React, Next.js, Vue, TypeScript (
.tsx,.ts) callingfetch(),axios,useSWR(),useQuery(), and property destructuring. - Test Discovery: Pytest, Unittest, Jest, Vitest, Playwright, Cypress.
🔑 Licensing & Tiers
| Tier | Price | Features |
|---|---|---|
| Community | $0 (Free) | Index topology, basic single-file symbol reachability, community support |
| Pro | $19/mo (or $180/yr) | Pre-Edit Breaking-Change Gate (PASS/WARN/BLOCK), full-stack contract chains, circular dependency interceptor, 2 seats |
| Team / CI Gate | $99/mo (or $990/yr) | Everything in Pro, 5 seats, git pre-commit hook enforcement, GitHub Actions / GitLab CI PR Gate integration |
Activate your Pro license:
blasttrace activate YOUR-LICENSE-KEY
🔒 Security & Privacy
BlastTrace runs 100% locally and air-gapped on your machine.
- Zero telemetry.
- Zero remote code scanning.
- Zero cloud database uploads.
- Your code never leaves your workstation.
© 2026 BlastTrace Inc. All rights reserved. Official website: blasttrace.com
Metadata
Release files for blasttrace 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| blasttrace-1.0.0-cp312-cp312-manylinux_2_39_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.39+ x86-64 | Details for blasttrace-1.0.0-cp312-cp312-manylinux_2_39_x86_64.whl |
Release files / blasttrace-1.0.0-cp312-cp312-manylinux_2_39_x86_64.whl
| Download URL | blasttrace-1.0.0-cp312-cp312-manylinux_2_39_x86_64.whl |
|---|---|
| Size | 870.3 kB |
| Tags | CPython 3.12 Linux glibc 2.39+ x86-64 |
|
SHA-256 checksum How to use checksums |
c0d79db69011426bd88a9fb81921fc321f550e03bd8a1e38a09f0c6636f00e0e
|
|
BLAKE2b-256 checksum How to use checksums |
1e14d8bcc1fe16ac0387bf5f47d6cb44800a9f6a5668e06a9432b9fcbb2db36b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for blasttrace 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.