psylligent / PageIndex
Code health
This codebase scores 5.8 out of 10 for code health, which we rate fair. It also scores maintainability 6.1 and static performance 9.7 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 20 of 140 files are git hotspots, and they average 4.8 — which is where the fixes pay off most.
Do next
1 thing worth doing in the week to Oct 7, the last indexed commit, 1 of them now.
Now
- Critical
Simplify
own_childreninpageindex/tree_optimize.pywhile the change is fresh1 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
- 1
- latest commit
- fix: unified-tree follow-ups in expand, intros and standard indexing (#5
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
- Lines of code
- 34.5K
Recent activity
All commitsCommits
- d57adcddfix: unified-tree follow-ups in expand, intros and standard indexing (#554)23h ago
- 6d23caf4Unify the document tree across local and cloud (#541)6d ago
- f0d67c12test: summary concurrency test waits for the expected overlap (#547)6d ago
- 60c8ff8afeat(sdk): node navigation helpers get_node, get_node_parent, get_node_path, get_node_map (#542)6d ago
- f279431eRestructure repo layout (#539)1w ago
- d2693d80ci(publish): gate releases on the live cloud tests again (#538)1w ago
Decisions
- Retry-loop behavior refined: truncation once and explicit exception on max retriesproposed · 11h ago
- Fail fast in Flash indexing when required environment keys are missingproposed · 11h ago
- Implement chat() front door over chat_completions and extend LiteLLM/Lite-routing Claude cache markingproposed · 11h ago
- Resolve paired cite tags and close only with citation they matchproposed · 11h ago
- Preserve MCP tool result blocks; let frameworks renderproposed · 11h ago
- Move document targeting to first user messageproposed · 11h ago
Everything we found
923 open
Every detector's open count by area, each with its worst example. An inventory, not a to-do list: the actions above are the part worth doing.
- worst item is critical severity. Code health672Prior defects · pageindex/utils.py38 findings · 8.0 deducted
- worst item is low severity. Refactoring87__init__+0.7 health, S effort · pageindex/flash/outline_assembly/candidates.py
- worst item is medium severity. Decisions60pageindex/client.py40 awaiting review · 20 hotspots ungoverned
- worst item is medium severity. Ownership104pageindex/client.py96% single-owner concentration, 45 commits in 90d
Composition
Open the graphExplore this codebase
- Docs252 pages across 4 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files140 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 1 entry points
- Code healthPer-file scores, 702 open findings, coverage and refactoring targets
- Knowledge graphEntities, communities, and the paths between them
- Change couplingFiles that keep changing together, mined from commit history
- CommitsChange-risk ranked history with agent provenance
- ContributorsBus factor, per-file maintainers, and the human/agent split
- StatsSize class, origin, lifetime churn, rhythm and records
- CostsWhat indexing this snapshot cost, by model and by run.