alasql / alasql
Code health
This codebase scores 9.1 out of 10 for code health, which we rate excellent. It also scores maintainability 9.0 and static performance 9.9 out of 10. The three are scored separately and never blended into one number.
Do next
4 things worth doing this quarter.
Worth planning
Break up queryfn3 (CCN 104, 308 lines)
src/38query.js:177
queryfn3 nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy.
- gain
- up to +0.7 health on this file(inferred)
- finding
- Nested complexity
- size
- CCN 104, 308 lines, nests 7 deep
- severity
- critical
Medium effort, worth a checkBreak up compile (CCN 48, 267 lines)
src/40select.js:155
compile nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy.
- gain
- up to +0.6 health on this file(inferred)
- finding
- Nested complexity
- size
- CCN 48, 267 lines, nests 4 deep
- severity
- medium
Medium effort, worth a checkDelete 31 unused symbols and files (1,022 lines)
Nothing in the graph reaches them, across 10 files; every reader and agent pays to skip them.
- symbols
- 31
- lines
- 1,022
- safe to delete
- Yes(inferred)
Medium effortBreak up doJoin (CCN 50, 119 lines)
src/39dojoin.js:73
doJoin has many independent paths through it.
- gain
- up to +1.1 health on this file(inferred)
- finding
- Complex method
- size
- CCN 50, 119 lines, nests 6 deep
- severity
- critical
Medium effort, worth a check
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 effort
- Lines of code
- 76.0K
Recent activity
All commitsCommits
Decisions
- Upload Scorecard results to GitHub code scanning dashboard (optional)proposed · 2mo ago
- Upload Scorecard results as artifacts (optional)proposed · 2mo ago
- Use publish_results to scale by extracting results via workflowproposed · 2mo ago
- Use GitHub OIDC token when publishing Scorecard resultsproposed · 2mo ago
- Schedule weekly Scorecard scans on Saturdaysproposed · 2mo ago
- Limit GitHub Scorecard workflow to default branchproposed · 2mo ago
Everything we found
700 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 health167Function hotspot · src/38query.js18 findings · 7.5 deducted
- worst item is medium severity. Refactoring23<anonymous>+1.5 health, XL effort · src/423groupby.js
- worst item is medium severity. Decisions36Revert case-insensitive distinct keyword with aggregations change36 awaiting review
- worst item is medium severity. Ownership440test/bun-setup.js100% single-owner concentration, 1 commits in 90d
- worst item is low severity. Dead code34src/orientdb/alasql-orientdb.jsUnreachable symbol (0 lines)
Composition
Open the graphExplore this codebase
- Docs0 pages across 7 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files812 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 635 entry points
- Code healthPer-file scores, 246 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.