2233admin / kline-orderbook-chart
markdownmain541a8d56.9K linessynced 1mo ago
Code health
9.8out of 10Excellent
This codebase scores 9.8 out of 10 on defect risk, which we rate excellent. It also scores maintainability 9.9 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: 1 of 40 files are git hotspots, and they average 8.4.
- Lines of code
- 6.9K
Recent activity
All commitsCommits
No commits indexed yet.
Decisions
- Re-issue license token if demo domain changesproposed
- Fallback to a 30-day watermarked trial on unapproved domainsproposed
- Narrow license scope to prevent indefinite free production hostingproposed
- Bind demo license token to a single domain and use local bypassproposed
- Require explicit chart.destroy() to prevent engine memory leaksproposed
- Lazy-load and globally cache the native engine moduleproposed
Needs attention
46 open- medium severity. ProposedRe-issue license token if demo domain changesAuto-proposed decision awaiting review
- medium severity. ProposedFallback to a 30-day watermarked trial on unapproved domainsAuto-proposed decision awaiting review
- medium severity. ProposedNarrow license scope to prevent indefinite free production hostingAuto-proposed decision awaiting review
- medium severity. ProposedBind demo license token to a single domain and use local bypassAuto-proposed decision awaiting review
- medium severity. ProposedRequire explicit chart.destroy() to prevent engine memory leaksAuto-proposed decision awaiting review
Where the risk concentrates
All 1 hotspotsRanked by prior bug fixes and change frequency, mined from full git history rather than from the code alone.
| File | Churn | Prior fixes | Maintainers | Commits 90d |
|---|---|---|---|---|
| useChart.jsdemo/src/composables | 87.5th | 0 | 1bus factor 1 | 5 |
Composition
Open the graphmarkdown 63%javascript 20%yaml 10%json 8%
Explore this codebase
- Docs0 pages across 21 modules
- ChatAsk this codebase a question and get an answer with its sources
- Files40 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 8 entry points
- Code healthPer-file scores, 20 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