repowiserepowise
Sign in

Repository

vzwjustin/Boundary-mapper
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsChange CouplingContributorsDecisions
ChatPro
By the Numbers
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowisevzwjustin/Boundary-mapper

Boundary-mapper

github.com/vzwjustin/boundary-mapper

fa49e4bmainsynced 18h ago

Files

29

Symbols

453

Docs

0

Dead Exports

2

Entry Points

2

Code HealthView report

Average health
6.6/10
Good
Hotspot health
10.0/10
Excellent
Open findings185Worst fileboundary_mapper/pattern_extract.py1.0/10
Maintainability7.6/10GoodPerformance19risks· 9.5/10

CostsView costs →

What this repo's indexing and doc generation cost, per sync.

Open the Costs page →

Attention Needed13

boundary_mapper/init.pyKnowledge Silo

100% single-owner concentration

boundary_mapper/runtime/trace_templates.pyDead Code

Safe to delete (50 lines)

boundary_mapper/main.pyKnowledge Silo

100% single-owner concentration

generate_bpftraceDead Code

Safe to delete (8 lines)

boundary_mapper/cli.pyKnowledge Silo

100% single-owner concentration

5 auto-proposed decisions awaiting reviewReview →

No commit history

Commit activity appears once git history is indexed.

Recent DecisionsView all

Avoid substring false positives by enforcing minimum command stem lengthproposed
18h ago · comment
Suppress findings for known intentional kernel-only surfacesproposed
18h ago · comment
Use heuristic suffix matching to treat 'not yet' names as reserved slotsproposed
18h ago · comment
Suppress findings for intentionally kernel-only and known-future/diagnostic surfacesproposed
18h ago · comment
Add boundary wiring tests for kernel↔userspace API detectionproposed
18h ago · git archaeology

No hotspot data

No churn or complexity hotspots detected in this repository.