repowiserepowise
Sign in
egraphs-good/egglog
OverviewDocsArchitectureKnowledge GraphFilesCode HealthSecurityRefactoring

People & History

CommitsContributorsDecisions
Chat
Stats
repowiserepowise
ExplorePricingDocs
Sign in
repowiseegraphs-good/egglog
EG
EG

egraphs-good / egglog

egraphs + datalog!

Rust★ 854
Use in your agentAsk this codebase

github.com/egraphs-good/egglog·Indexed at 9063586·17d ago·Up to date with upstream

About this codebase

184 files and 6,360 symbols in 14 modules, led by Rust (147 files) and Python (7).

Built from the index

Start reading

  • Knowledge graph184 files and how they depend on each other.→
  • Adaptive 8-bit LSB radix sort for single-column rebuildDecisionProposed decision, from a pull request.→

Code health

4.0out of 10Needs work

This codebase scores 4.0 out of 10 for code health, which we rate needs work. It also scores maintainability 4.3 and static performance 9.8 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 30 of 184 files are git hotspots, and they average 2.4 — which is where the fixes pay off most.

Full health report →

On the leaderboards:#9 of 10 Rust repos

Do next

1 thing worth doing in the week to Sep 4, the last indexed commit, 1 of them now.

Now

  • High

    Simplify step_rules_with_scheduler in src/scheduler.rs while the change is fresh

    1 commit in the last 7 days added or worsened 2 critical or high findings here, still open. Fixing now costs less than after the next change.

    serious findings
    2
    critical
    0
    latest commit
    Fix scheduler semantics and node counting
    Small effort

Improve what Repowise can see

  • Add a test coverage report

    Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.

    line coverage
    Unknown, no report
    Small effort
All actions in the Overview →

Use egraphs-good/egglog in your agent

Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.

https://api.repowise.dev/mcp/egraphs-good/egglog

One command, run anywhere. Adds the server to your local Claude Code config.

Docs
bash
claude mcp add --transport http repowise https://api.repowise.dev/mcp/egraphs-good/egglog \
  --header "Authorization: Bearer rw_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
The snippet shows a placeholder key. Generate one to get a copyable secret.
Sign in and create an API key to connect.Sign in

This repo is public, so anyone with a Repowise account and an API key can connect.

Try asking

  • get_overview()
  • get_answer("how is egglog put together?")
  • get_why("why is egglog structured this way?")

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.

Go deeper

  • OverviewEverything the index found, what changed this week, commits and decisions.→
  • DocumentationModule-by-module documentation, 295 pages, 0 written by a model.→
  • ArchitectureDependency graph, layers and third-party dependencies.→
  • Code healthEvery file's score, the findings behind it, tests and refactoring plans.→
  • CommitsEach commit's effect on code health, with agent provenance.→
  • ContributorsWho owns what, and where one person holds most of the knowledge.→
  • DecisionsArchitectural decisions mined from commits and pull requests.→
  • Ask this codebaseSign inGrounded answers over the indexed code.→

Maintain this repo? Claim the page

Sign in with GitHub and we check that you are an admin or maintainer of egraphs-good/egglog. Then add a badge to the README that links readers here.

Use this repo from Claude or ChatGPT

Add this URL as a custom connector and sign in with repowise when asked. No API key to copy.

https://api.repowise.dev/mcp/egraphs-good/egglog
Sign up to connect

For maintainers

Add a badge to your README

Every badge is public, cached, and updates on its own after every index. Nothing to install.

Repowise badge

Links to this page, with no score on it. Adding it also re-indexes the repo every week.

Repowise badge preview
[![repowise.dev](https://api.repowise.dev/badge/wiki/egraphs-good/egglog.svg)](https://repowise.dev/repo/egraphs-good/egglog?src=badge_wiki)

Code health badge

The repo's health score out of 10, from the latest index.

Code health badge preview
[![repowise.dev code health](https://api.repowise.dev/badge/health/egraphs-good/egglog.svg)](https://repowise.dev/repo/egraphs-good/egglog?src=badge_health)

Code health card

A larger card with the score, its change since the last index, and when it was measured. The HTML version follows the reader's light or dark theme.

Code health card preview
[![repowise.dev code health](https://api.repowise.dev/badge/health/egraphs-good/egglog.svg?style=card)](https://repowise.dev/repo/egraphs-good/egglog?src=badge_card)

How egraphs-good/egglog works

egraphs + datalog! This page is a map of the egraphs-good/egglog repository, written primarily in Rust, rebuilt from the source each time it is indexed. Repowise parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the architectural decisions into documentation you can read here or query through MCP.

The codebase has 184 files and 6,360 symbols in 14 modules, led by Rust, Python and Makefile. Code health is 4.0 out of 10, rated needs work.

Use the links above to open each view, or connect this repository to your agent for grounded answers inside Claude, Cursor, Codex or VS Code.