ladybirdbrowser / ladybird

GitHub

Code

How ladybirdbrowser/ladybird is laid out, and where to start for common changes.

Architecture grade

score 100/100

Import cycles

lower is better

Files mapped

12 imports between them

100%

Layering

of imports point one way

From the map of which files import which, built when the code was last read in full. It shows what depends on what, not a reading order.

Module map

Shade by

3 modules, 0 links. A link means one module imports another; thicker lines mean more imports. Links come from 94 of 6,070 source files, so the real counts are higher. Select a module to trace it: blue lines go to what it uses, orange lines come from what uses it.

Where to start reading

Repository root
Repository root
Likely public API
Likely public API
Likely start-up file
Likely start-up file
Suggested starting pointAI
Suggested starting pointAI

Find files for a task

Add a new IPC service

Add a new web standard feature to the rendering engine

Extend DOM element classes with new properties/methods following Libraries/LibWeb/ARIA/ARIAMixin.cpp pattern
Add JavaScript bindings in LibJS/ABI for script access

Add a new network protocol handler

Create protocol implementation in RequestServer following Services/RequestServer/AIA.cpp pattern
Define DNS or TLS requirements if needed using Libraries/LibDNS and Libraries/LibTLS
Integrate with LibRequests HTTP client following Libraries/LibRequests/ALPNHttpVersion.h
Add build configuration and link against RequestServer in CMakeLists.txt

Add a new media codec or audio device backend

Implement codec in Libraries/LibMediaCodecs following Libraries/LibMediaCodecs/AudioBlockTiming.h structure
For audio devices, add platform-specific backend (e.g. macOS) in Services/AudioServer/AudioDevicesCoreAudio.cpp
Integrate audio buffer management from Libraries/LibMedia/Audio/AudioBuffer.h
Expose through IPC via Libraries/LibAudio/AudioClient.ipc

Change the public API

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 points237 per file on average
Code issues0 errors, 102 warnings
Largest file4,087 lines
Hotspot load10 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

CIGitHub Actions17 workflows
Tests29,073 test filesRust test · 4.8 test files per source file (file count, not coverage)
Dependency updatesNo config detected

Test folders: Libraries/LibWasm/Engine/tests/fixtures · Libraries/LibJS/Flap/tests · Libraries/LibWasm/Engine/tests

Hotspots

Libraries/LibWebView/Application.cpp100 commits in 180 days · 570 branch points
Services/WebContent/ConnectionFromClient.cpp100 commits in 180 days · 638 branch points
Libraries/LibSandbox/Seccomp.cpp37 commits in 180 days · 88 branch points
UI/Qt/Application.cpp93 commits in 180 days · 229 branch points
Services/RequestServer/ConnectionFromClient.cpp55 commits in 180 days · 204 branch points
Services/WebDriver/Session.cpp22 commits in 180 days · 72 branch points
Services/WebContent/DevToolsDebugger.cpp22 commits in 180 days · 166 branch points
Services/WebDriver/Client.cpp19 commits in 180 days · 41 branch points

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