repowiserepowise
Sign in
ltpk/charging-optimizer
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowiseltpk/charging-optimizer

Code health for ltpk/charging-optimizer

Repowise scores ltpk/charging-optimizer at 6.3 out of 10 for defect risk, which reads as fair. There are 43 open findings across the three pillars, and the lowest-scoring file is optimization.ts at 2.4. Scores are computed from complexity, duplication, churn and git fix history, not from a linter.

Code Health

Per-file health scores from complexity, duplication, coverage, churn, and ownership markers, ranked into a fix-next queue, with risk, security, and trend in one place.

Hotspots

0

high-churn files

Silos

0

owner >80%

Dead Code

0

findings

Stale Decisions

0

need review

Security

0

high findings