zpqrtbnk / test-repo
yamlmaster4b6d6bc965 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.8 and static performance risk 10.0 out of 10. The three are scored separately and never blended into one number.
- Lines of code
- 965
Recent activity
All commitsCommits
No commits indexed yet.
Decisions
- we don't want to add another commit on top of the merge, just shoobi itproposed · 1mo ago
- because we fetched both other and master with depth=1 we have no history and therefore no way to…proposed · 1mo ago
- see this just creates the symlink in Git - works on Windows BUT will be checked out as a file and…proposed · 1mo ago
- symlink via pwsh this creates a 'bang' file that contains 'duh' on local machine, it fails…proposed · 1mo ago
- note: we may eventually need to paginate and then releases.headers should contain what we need?…proposed · 1mo ago
- note: getReleaseByTag only returns published releasesproposed · 1mo ago
Needs attention
22 open- medium severity. Proposedwe don't want to add another commit on top of the merge, just shoobi itAuto-proposed decision awaiting review
- medium severity. Proposedbecause we fetched both other and master with depth=1 we have no history and therefore no way to…Auto-proposed decision awaiting review
- medium severity. Proposedsee this just creates the symlink in Git - works on Windows BUT will be checked out as a file and…Auto-proposed decision awaiting review
- medium severity. Proposedsymlink via pwsh this creates a 'bang' file that contains 'duh' on local machine, it fails…Auto-proposed decision awaiting review
- medium severity. Proposednote: we may eventually need to paginate and then releases.headers should contain what we need?…Auto-proposed decision awaiting review
Composition
Open the graphyaml 68%javascript 18%markdown 9%json 5%
Explore this codebase
- Docs11 pages across 10 modules
- ChatAsk this codebase a question and get an answer with its sources
- Files22 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 1 entry points
- Code healthPer-file scores, 4 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