repowiserepowise
Sign in
litestar-org/litestar
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
Chat
Stats
repowiserepowise
ExplorePricingDocs
Sign in
repowiselitestar-org/litestar
LI
LI

litestar-org / litestar

pythonmain7cccc5e81.4K linessynced 1d ago

Code health

7.8out of 10Good

This codebase scores 7.8 out of 10 on defect risk, which we rate good. It also scores maintainability 8.8 and static performance risk 10.0 out of 10. The three are scored separately and never blended into one number. The files you change most are the weak spot: 2 of 1,118 files are git hotspots, and they average 4.5.

Full health report →
Documentation1,203pages0 with model-written prose, 1,203 built from the indexScore validation14/209.78× baselineOf the 20 lowest-health files, 14 were bug-fixed in the last 6 months — 9.78× the 7% baselineDead code19exportsUnused exports that nothing in the graph reaches
Lines of code
81.4K
Files
1,118
Symbols
6,844
Modules
7
Languages
10

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Starlite parameter types: route handlers as optional sequenceproposed · 1d ago
  • Warn when sync handlers lack explicit sync_to_threadproposed · 1d ago
  • Unify hook handler signaturesproposed · 1d ago
  • Migrate documentation to Sphinxproposed · 1d ago
  • Deprecate subclassing route handler decoratorsproposed · 1d ago
  • Deprecate litestar.contrib.sqlalchemyproposed · 1d ago

Needs attention

51 open
  • medium severity. ProposedStarlite parameter types: route handlers as optional sequenceAuto-proposed decision awaiting review
  • medium severity. ProposedWarn when sync handlers lack explicit sync_to_threadAuto-proposed decision awaiting review
  • medium severity. ProposedUnify hook handler signaturesAuto-proposed decision awaiting review
  • medium severity. ProposedMigrate documentation to SphinxAuto-proposed decision awaiting review
  • medium severity. ProposedDeprecate subclassing route handler decoratorsAuto-proposed decision awaiting review

Where the risk concentrates

All 2 hotspots →

Ranked by prior bug fixes and change frequency, mined from full git history rather than from the code alone.

FileChurnPrior fixesMaintainersCommits 90d
test_schema.pytests/unit/test_openapi99.9th9bug magnet196
schema.pylitestar/_openapi/schema_generation99.0th7bug magnet236

Composition

Open the graph →
python 97%yaml 1%html 0%markdown 0%json 0%Other 1%

Explore this codebase

  • Docs1,203 pages across 7 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files1,118 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 13 entry points→
  • Code healthPer-file scores, 2,004 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→