meta / astryx
Code health
Hotspots average 4.7, the place fixes pay off most.
Explore this codebase
- Code health map166hotspots across 11,404 files
- Ownership2,007sole-owned files: one author, no second reader
- Architecture7modules, 31 entry points
- Decisions108recorded, of which 0 in force and 108 background
- Refactoring526open opportunities, one per file
- TestsNo coverage report yet. Run your tests with coverage on, then add the report:
AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts
Do next · 6
6 things worth doing in the week to Nov 19, the last indexed commit.
Worth planning
Tidy the code shape this week's commits left: 47 findings in 33 files
21 commits in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with
packages/core/src/Lightbox/Lightbox.tsx(4 findings): tidying it while the change is fresh costs less than after the next one.- code-shape findings
- 47
- files
- 33
- commits
- 21
Large effortSimplify
reverseToFileinpackages/cli/api/render/_adapter.mjs: tests reach it, and fixes keep landingChanged 24 times in 90 days, and 14 of those commits were bug fixes.
- commits in 90 days
- 24
- bug-fix commits
- 14
- line coverage
- Unknown, no report
- tests that reach it
- 9 test files, call graph(inferred)
Large effort, worth a checkSimplify
compileThemeinpackages/cli/api/theme-edit/_settings.mjs: tests reach it, and fixes keep landingChanged 20 times in 90 days, and 14 of those commits were bug fixes.
- commits in 90 days
- 20
- bug-fix commits
- 14
- line coverage
- Unknown, no report
- tests that reach it
- 54 test files, call graph(inferred)
Large effort, worth a checkSimplify
changeOnceinpackages/cli/api/theme-edit/_edit.mjs: tests reach it, and fixes keep landingChanged 17 times in 90 days, and 15 of those commits were bug fixes.
- commits in 90 days
- 17
- bug-fix commits
- 15
- line coverage
- Unknown, no report
- tests that reach it
- 407 test files, call graph(inferred)
Large effort, worth a checkSimplify
draftAnswerinpackages/cli/api/theme-edit/_how-question.mjs: tests reach it, and fixes keep landingChanged 18 times in 90 days, and 14 of those commits were bug fixes.
- commits in 90 days
- 18
- bug-fix commits
- 14
- line coverage
- Unknown, no report
- tests that reach it
- 7 test files, call graph(inferred)
Large effort, worth a check
Everything we found
5 areas
Every detector's open count by area. The actions above are the part worth doing.
- Code health9,250 open findingsCriticalCo-change scatter · packages/cli/api/theme-edit/_settings.mjs378 findings · 15.5 deducted
- Refactoring526 open opportunitiesMediumdefineCommand+1.8 health, M effort · packages/cli/clients/cli/lib/define-command.mjs
- Doc drift7Mediumpackages/core/README.mdLink points at #xds-cli, which packages/core/README.md no longer declares.
- Decisions0 drifting from the codeMediumpackages/cli/api/theme-edit/_how-question.mjsHigh-churn file with no governing decision
- Ownership2,007 sole-owned filesMediumpackages/cli/api/doctor/doctor.mjsOne author, no second reader