repowiserepowise
Sign in
boolean-maybe/tiki
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowiseboolean-maybe/tiki
TI
TI

boolean-maybe / tiki

gomain872cc5f89.6K linessynced 18h ago

Code health

7.0out of 10Good

This codebase scores 7.0 out of 10 on defect risk, which we rate good. It also scores maintainability 8.6 and static performance risk 9.9 out of 10. The three are scored separately and never blended into one number. The files you change most are the weak spot: 93 of 543 files are git hotspots, and they average 4.2.

Full health report →
Documentation784pages0 with model-written prose, 784 built from the indexScore validation12/204.79× baselineOf the 20 lowest-health files, 12 were bug-fixed in the last 6 months — 4.79× the 13% baselineDead code23exportsUnused exports that nothing in the graph reaches
Lines of code
89.6K
Files
543
Symbols
4,462
Modules
22
Languages
7

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Preserve historical vibrant gradient semantics for algoLift, with inverse orderingproposed · 18h ago
  • Preserve historical gradient semantics for algoAccentproposed · 18h ago
  • Degrade gradient behavior to solid when gradients are disabledproposed · 18h ago
  • Encapsulate solid-vs-gradient rendering behind Paint strategyproposed · 18h ago
  • Differentiate absent vs explicitly present fields (nil allowed)proposed · 18h ago
  • Presence-safe identity and audit fields live outside generic Fields mapproposed · 18h ago

Needs attention

39 open
  • medium severity. ProposedPreserve historical vibrant gradient semantics for algoLift, with inverse orderingAuto-proposed decision awaiting review
  • medium severity. ProposedPreserve historical gradient semantics for algoAccentAuto-proposed decision awaiting review
  • medium severity. ProposedDegrade gradient behavior to solid when gradients are disabledAuto-proposed decision awaiting review
  • medium severity. ProposedEncapsulate solid-vs-gradient rendering behind Paint strategyAuto-proposed decision awaiting review
  • medium severity. ProposedDifferentiate absent vs explicitly present fields (nil allowed)Auto-proposed decision awaiting review

Where the risk concentrates

All 93 hotspots →

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

FileChurnPrior fixesMaintainersCommits 90d
store_test.gostore/tikistore99.8th01bus factor 19
plugin_selection_test.gocontroller99.5th31bus factor 113
parser_test.goplugin99.3th21bus factor 110
input_router.gocontroller99.1th11bus factor 116
persistence.gostore/tikistore98.9th11bus factor 111

Composition

Open the graph →
go 80%markdown 18%yaml 1%makefile 0%shell 0%Other 0%

Explore this codebase

  • Docs784 pages across 22 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files543 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 14 entry points→
  • Code healthPer-file scores, 1,860 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→