nodebox / nodebox
Code health
This codebase scores 7.6 out of 10 for code health, which we rate good. It also scores maintainability 7.5 and static performance 9.9 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 1 of 328 files are git hotspots, and they average 8.0 — which is where the fixes pay off most.
Do next
1 thing worth doing this quarter.
Worth planning
Delete 21 unused symbols and files (135 lines)
Nothing in the graph reaches them, across 3 files; every reader and agent pays to skip them.
- symbols
- 21
- lines
- 135
- safe to delete
- Yes(inferred)
Small effort
Improve what Repowise can see
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
- line coverage
- Unknown, no report
Small effortReview the 7 proposed decisions
None is accepted yet, so nothing can drift from one and agents get no enforced guidance from them.
- proposed
- 7
- accepted
- 0
Medium effort
- Lines of code
- 36.4K
Recent activity
All commitsCommits
- 28124061Draw handles in screen space so they stay a constant size when zooming4mo ago
- f4627393Render on a conflated background thread for smooth parameter dragging4mo ago
- 953dfaeeCache node render results across renders4mo ago
- 971d3099Release v3.1.04mo ago
- 8d3b24c5ci: move JS actions to Node 24; quiet brew ant warning4mo ago
- dab1022aci: drop temporary PR-branch trigger now that the pipeline is verified4mo ago
Decisions
- Load NodeBox files as UTF-8 instead of default platform encodingproposed · 1mo ago
- Use a long-lived render thread with latest-wins mailboxproposed · 1mo ago
- Fix notarization: stop signing the app bundle with --deepproposed · 1mo ago
- Fix notarization: sign native libs inside nodebox.jarproposed · 1mo ago
- Add reproducible native installer builds via GitHub Actionsproposed · 1mo ago
- Load NodeBox files using UTF-8 instead of platform default encodingproposed · 1mo ago
Everything we found
729 open
Every detector's open count by area, each with its worst example. An inventory, not a to-do list: the actions above are the part worth doing.
- worst item is critical severity. Code health343Untested hotspot · src/main/java/nodebox/client/NodeBoxDocument.java20 findings · 8.6 deducted
- worst item is medium severity. Refactoring63actionPerformed+1.3 health, S effort · src/main/java/nodebox/client/PortAttributesEditor.java
- worst item is medium severity. Decisions8src/dev/java/nodebox/PackageSigner.java7 awaiting review · 1 hotspots ungoverned
- worst item is medium severity. Ownership292src/dev/java/nodebox/PackageSigner.java100% single-owner concentration, 3 commits in 90d
- worst item is low severity. Dead code23GeometryContextUnreachable class (26 lines)
Composition
Open the graph- java96%
- python3%
- clojure<1%
- shell<1%
Explore this codebase
- Docs664 pages across 4 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files328 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 1 entry points
- Code healthPer-file scores, 360 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.