CODEmd.dev - Free commit graphs, bug detection, and code search

Connect GitHub

Option A — sign in to GitHub, choose a repository, and get commit graphs, callgraphs, bug detection, and code search instantly.

Choose from your GitHub repositories

Authorize CODEmd.dev and choose a repository from your GitHub installation.

Connect GitHub to choose a repository from your installation.

1Connect GitHub 2Install GitHub Repo Permissions App

No GitHub repository connected yet.

Connect your product code to get started.

Files Reviewed

829

From the connected codebase

Languages

By known extensions

Extensions

Unique suffixes

Mapped Items

2935

Interactive code map

Connections

626

How files and features relate

TODO Items

Extracted from comments

Lines of Code

Source files

Approx Tokens

LOC x 10

Step 1 · Free Repo Analysis

Analyze your repository — choose one of the three ways below.

Connect GitHub and pick a repository above, paste a GitHub URL, or upload a code archive. Any one of the three starts the same free analysis.

In minutes, get a daily commit graph, a navigable callgraph, fast code search, and automatic bug detection — all free.

For every commit, CODEmd.dev also finds and runs the tests that already cover your change — free, no AI needed. It catches what a quick diff read misses, like a break several calls away from the function you actually edited.

Every real test that touches the change — not just a filename match.
Coverage-confirmed: a pass means those lines actually ran.
Catches breaks anywhere down the call chain, not just the edited function.

Option B — Paste a GitHub URL

Sample repository shown by default: medusajs/dtc-starter. Replace it with your own GitHub repository when you are ready.

Option C — Upload code archive

Feature-level development & safety

The complete product workflow, on one page

Create and organize features, follow every code change through its impact and tests, attach operational evidence, and make an evidence-backed ship, hold, or rollback decision. Every area below remains visible; the sidebar only scrolls to the corresponding detailed tools.

01 · COMMITS

Changes and commits

Recent repository work, authors, affected files, and feature attribution.

Waiting for analysis

Connect and analyze a repository to load commit evidence.

02 · IMPACT

Change impact

Callgraph reach, affected product areas, and implementation scope.

Unknown

Impact appears after the callgraph is built.

03 · TESTS

Targeted tests

Relevant tests, recorded runs, coverage evidence, and test lag.

Not checked

Test evidence appears after analysis or a test run.

04 · BUGS

Bugs, issues, and defects

Active failures, fixed defects, recurring breakage, and environment results.

No evidence

Recorded defects will appear here.

05 · STATIC FINDINGS

Static findings

Deterministic bug, structural, callgraph, and cross-file signals.

Not loaded

Static findings appear after repository analysis.

06 · FEATURES

Feature catalog and sub-features

Create, edit, summarize, organize, hide, restore, and map features to implementation evidence.

No catalog

Detected and managed features will appear here.

07 · DASHBOARD

Feature readiness and release decision

Evidence-backed status, merge risk, and the next action to take before shipping.

Insufficient evidence

Readiness is calculated from mapping, change, test, defect, and operational evidence.

08 · SECURITY

Security exposure

External-input paths, sensitive sinks, security findings, and unknown evidence.

Not analyzed

Security stays unknown until evidence is available.

09 · PRODUCT ANALYSIS

Product analysis

Product identity, feature coverage, notes, telemetry, and go-to-market context.

Waiting for analysis

Product analysis appears after feature extraction.

10 · SEARCH RESULTS

Code intelligence search results

Grounded answers, matching functions, supporting documentation, and result graphs.

Ready for a question

Use Code Intelligence Search below; the latest result remains visible in that section and is summarized here.

Code Map

File Connections Map Double-click nodes to walk file relationships.

Analyze your code to create the navigable file graph.

Function Callgraph Double-click nodes to follow function and UI paths.

Analyze your code to create the navigable function callgraph.

Daily Product Change and Commit Summary

See what changed recently, who changed it, and which product areas may be affected.

Connect GitHub and analyze your code to see recent product changes.

Run Playwright and Callgraph Tests

Once analysis above finishes, CODEmd.dev finds and runs the tests that already cover each commit and shows you the bugs and issues found — no extra step needed (see the Daily Product Change section above). Optionally, add your product's live URL here too, to also run real browser checks with Playwright. Either way, we write tests you can copy into your own repo if you want them.

Optional. Use any public HTTP, HTTPS, SMTP, or product endpoint your users interact with. Results appear in the Playwright Tests panel below.

Playwright Tests

Comprehensive automated browser testing against your Product URL: page load/console errors, accessibility violations, performance timing, and full-page screenshots.

Set a Product URL above, then run Playwright tests.

Generate Test Suite

Generate a custom pytest + Playwright test file built from your own routes, UI elements, and user flows — not generic boilerplate. Uses the Product URL set above.

Set a Product URL above, then generate a test suite.

Code Intelligence Search

See how CODE.md makes your LLM better

Ask CODEmd.dev anything about your codebase

Trace features, investigate errors, understand change impact, and map user actions to implementation. Every answer is grounded in repository evidence.

Evidence-backed answers

Ask CODEmd.dev about this repo

Ask a plain-English question and get an answer backed by product, user, and code evidence.

Open to review the details CODEmd.dev will use before generating an answer.

Search details will appear here after you run a search.

CODE.md

Generated architecture and behavior contract from the completed repository analysis.

Analyze a repository to generate CODE.md.

Search Graphs

Search Result Map Question-specific map generated from search results.

Run a search to see the map for that specific question. This does not replace the Code Map.

Search graph detail

File and Function Callgraph Choose a file or function to create a smaller navigable graph.

Analyze a repository, choose a file, then optionally choose a function.

Open to view detected languages and file counts.

Open to inspect the most common file extensions.

Extension	Files

Open to view GitHub stars, branch, license, and other repository details.

Static Quality Signals and Bugs

Fast checks from parsed source and callgraphs. These are not LLM guesses; each item includes a confidence level.

Dead code Unreachable branches Missing error handling Dangerous fan-in / fan-out Circular dependencies API misuse patterns Incorrect async usage Mutation bugs Missing null checks Shadowed variables Parameter mismatch Unused imports / variables Missing returns Cross-file type drift High-risk recent changes

Static Callgraph Bugs

Bug	Where	Confidence	Status	Resolve Bug
Analyze your code to see defensible bug checks.

Structural Mistakes

Signal	Where	Confidence	Status	Resolve Bug
Analyze your code to see structural checks.

Callgraph Mistakes

Signal	Where	Confidence	Status	Resolve Bug
Analyze your code to see callgraph checks.

Cross-file Mistakes

Signal	Where	Confidence	Status	Resolve Bug
Analyze your code to see cross-file checks.

Code Areas That May Need Review

Functions with no callers and no callees in the code map. Tick a row once you've confirmed it's okay.

Okay	Code area	File	Line	Used by	Uses
Analyze your code to review isolated areas.

Product Description

Generate a product description to populate this panel.

Feature Implementation Graph

Feature to UI and Code Map Start from feature anchors, then walk UI and implementation links.

Analyze your code to connect features to UI and implementation paths.

Feature List

Feature Name	Description	Match
Analyze your code to populate editable feature names.

TODO Work Items

Scope	Target	Line	TODO Item

TODO

Product, file, and function TODOs you've created. Delete one once you're done with it.

Connect a repository to see your TODOs.

Code Comments

Search for a function, class, file, or behavior, then attach a note.

Kind	File	Line	Text

Connect Google Analytics

Connect GA4 to load user actions, error events, user journey maps, and suggested fixes.

Analytics Connect

Load GA events anytime; code maps appear when analysis is available.

Connect Google Analytics to load user activity.

Connect analytics Reconnect analytics

User Activity Map

Connect Google Analytics to see which user actions connect to which areas of the code.

User Activity Events Load user activity to see GA rows.

Time	Action	Events	Function / target	Map
No user activity events loaded yet.

Mapped Code Areas Load user activity to see GA events matched to code.

Code area	Events	Evidence
No mapped user activity loaded yet.

Load user activity to see each user action path.

User action paths will appear here after activity is loaded.

Suggested Fixes

When users hit errors, CodeVal connects the issue to the likely code area and suggests a fix. Nothing is changed automatically.

Load user activity to check for product errors.

No user-facing errors loaded yet.

Generated Files

Open generated JSON, graph, summary, and index files from the latest loaded analysis.

File	Type	Source	Open
Analyze your code to see generated files.

See what's really going on in your codebase.