repowiserepowise
Sign in
reconurge/flowsint
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowisereconurge/flowsint
FL
FL

reconurge / flowsint

typescriptmain95e0ab977.4K linessynced 1h ago

Code health

8.7out of 10Excellent

This codebase scores 8.7 out of 10 on defect risk, which we rate excellent. It also scores maintainability 8.9 and static performance risk 9.9 out of 10. The three are scored separately and never blended into one number. The files you change most are the weak spot: 3 of 778 files are git hotspots, and they average 4.5.

Full health report →
Documentation952pages0 with model-written prose, 952 built from the indexScore validation6/203.65× baselineOf the 20 lowest-health files, 6 were bug-fixed in the last 6 months — 3.65× the 8% baselineDead code262exportsUnused exports that nothing in the graph reaches
Lines of code
77.4K
Files
778
Symbols
3,917
Modules
57
Languages
10

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Mock the graph service to avoid Neo4j calls in template testsproposed · 1h ago
  • Enable foreign key support for SQLite in testsproposed · 1h ago
  • Use an in-memory SQLite session for testingproposed · 1h ago
  • Mock Logger to avoid database calls during testsproposed · 1h ago
  • Use dummy Neo4j credentials for tests due to eager singleton constructionproposed · 1h ago
  • Set a test master key for vault testsproposed · 1h ago

Needs attention

46 open
  • medium severity. ProposedMock the graph service to avoid Neo4j calls in template testsAuto-proposed decision awaiting review
  • medium severity. ProposedEnable foreign key support for SQLite in testsAuto-proposed decision awaiting review
  • medium severity. ProposedUse an in-memory SQLite session for testingAuto-proposed decision awaiting review
  • medium severity. ProposedMock Logger to avoid database calls during testsAuto-proposed decision awaiting review
  • medium severity. ProposedUse dummy Neo4j credentials for tests due to eager singleton constructionAuto-proposed decision awaiting review

Where the risk concentrates

All 3 hotspots →

Ranked by prior bug fixes and change frequency, mined from full git history rather than from the code alone.

FileChurnPrior fixesMaintainersCommits 90d
models.pyflowsint-core/src/flowsint_core/core97.5th044
custom_type_service.pyflowsint-core/src/flowsint_core/core/services96.6th033
to_fraudscore.pyflowsint-enrichers/src/flowsint_enrichers/ip91.2th343

Composition

Open the graph →
typescript 51%python 42%markdown 3%yaml 2%json 1%Other 2%

Explore this codebase

  • Docs952 pages across 57 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files778 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 30 entry points→
  • Code healthPer-file scores, 1,278 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→