repowiserepowise
Sign in
2233admin/asm-hall-of-shame
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowise2233admin/asm-hall-of-shame
AS
AS

2233admin / asm-hall-of-shame

cmaine5aa8325.8K linessynced 1h 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.6 and static performance risk 10.0 out of 10. The three are scored separately and never blended into one number.

Full health report →
Documentation113pages0 with model-written prose, 113 built from the indexDead code28exportsUnused exports that nothing in the graph reaches
Lines of code
5.8K
Files
109
Symbols
346
Modules
34
Languages
5

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Keep x87 stack balanced by using read-only input and separate output bufferproposed · 1h ago
  • Use single-shot timing loop to avoid subnormal normalization effectsproposed · 1h ago

Needs attention

22 open
  • medium severity. ProposedKeep x87 stack balanced by using read-only input and separate output bufferAuto-proposed decision awaiting review
  • medium severity. ProposedUse single-shot timing loop to avoid subnormal normalization effectsAuto-proposed decision awaiting review
  • medium severity. Knowledge siloclflush/clflush.c100% single-owner concentration
  • medium severity. Knowledge silocpuid/cpuid.c100% single-owner concentration
  • medium severity. Knowledge silodenormal/denormal.c100% single-owner concentration

Composition

Open the graph →
c 35%makefile 32%markdown 31%python 1%shell 1%

Explore this codebase

  • Docs113 pages across 34 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files109 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 0 entry points→
  • Code healthPer-file scores, 37 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→