repowiserepowise
Sign in

Repository

KGerring/reg
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsChange CouplingContributorsDecisions
ChatPro
By the Numbers
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowiseKGerring/reg

reg

github.com/kgerring/reg

ed517e9mastersynced 21h ago

Files

25

Symbols

478

Docs

0

Dead Exports

18

Entry Points

0

Code HealthView report

Average health
9.3/10
Excellent
Hotspot health
10.0/10
Excellent
Open findings81Worst filereg/tests/test_registry.py8.7/10
Maintainability9.4/10ExcellentPerformance1risk· 10.0/10

CostsView costs →

What this repo's indexing and doc generation cost, per sync.

Open the Costs page →

Attention Needed18

doc/conf.pyKnowledge Silo

99% single-owner concentration

perf.pyDead Code

Safe to delete (190 lines)

examples/reg_example.pyKnowledge Silo

83% single-owner concentration

profdispatch.pyDead Code

Safe to delete (130 lines)

perf.pyKnowledge Silo

84% single-owner concentration

15 auto-proposed decisions awaiting reviewReview →

No commit history

Commit activity appears once git history is indexed.

Recent DecisionsView all

Cache per-class dispatch method instead of attaching to classproposed
21h ago · comment
Introduce an auto_methodify functionalityproposed
21h ago · git archaeology
Eliminate the Registry story; go directly to Predicate registryproposed
21h ago · git archaeology
Remove PredicateRegistry from the APIproposed
21h ago · git archaeology
Rewrite arginfo and expose default informationproposed
21h ago · git archaeology
Drop Python 2/3.3 support; add Python 3.5-3.7proposed
21h ago · git archaeology

No hotspot data

No churn or complexity hotspots detected in this repository.