RepoPilot

morluto / rea

Search morluto/rea

GitHub

Code

How morluto/rea is laid out, and where to start for common changes.

There is no import map for this report yet.

Where to start reading

  1. Repository root
  2. Repository root
  3. Likely start-up file
  4. Suggested starting pointAI
  5. Suggested starting pointAI
  6. Suggested starting pointAI
  7. Suggested starting pointAI
  8. Suggested starting pointAI

Find files for a task

AI

Add support for a new binary analysis tool

  • Register the tool in the main CLI router by adding a case to `src/cli/analysisSelector.ts` that selects your analyzer based on binary type.

Add a new runtime instrumentation capability

  • Register in CLI analysis selector so it gets invoked for appropriate runtime targets (e.g., specific process types or platforms).

Add a new artifact parsing or extraction handler

  • Wire into the analysis context query system (`src/application/AnalysisContextQueries.ts`) so artifacts are discoverable by other tools.

Trace runtime behavior

Add or update tests

Change build or automation

RepoPilot lists up to 500 files, so a file missing here may still exist.

  • Files marked “likely” are guessed from their names.
  • Some entry points named in the manifest are build output or are missing from the file list, so their source is not shown.

Code quality and hotspots

Largest source files

  • Branch points202 per file on average
  • Code issues0 errors, 32 warnings
  • Largest file3,232 lines
  • Hotspot load10 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions30 workflows
  • Tests1,990 test filesPytest · Jest/Vitest · 0.99 test files per source file (file count, not coverage)
  • Dependency updatesNo config detected

Test folders: src/apktool · experiments/analysis-efficiency · src/adb

Hotspots

Files that change often and branch heavily, highest first. Complexity is 0–100 from branch and nesting counts.