RepoPilot

mozilla-ocho / llamafile

Search mozilla-ocho/llamafile

GitHub

Code

How mozilla-ocho/llamafile 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. Likely start-up file
  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 Programming Language Highlighter

  • Register highlighter in main highlight dispatcher switch statement

Add a New Hardware Acceleration Backend

  • Register backend detection in compute dispatcher
  • Add platform-specific build configuration

Extend the REST API with a New Endpoint

  • Define request/response handler in chatbot API router
  • Implement backend logic or delegate to existing inference engine

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.

Code quality and hotspots

Largest source files

  • Branch points3022 per file on average
  • Code issues2 errors, 105 warnings
  • Largest file260,489 lines
  • Hotspot load0 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions6 workflows
  • Tests38 test filesPytest · 0.10 test files per source file (file count, not coverage)
  • Dependency updatesNo config detected

Test folders: tests/integration/tests · tests · tests/sgemm

Hotspots

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.