Skip to content

Github · GitHub Repository Radar

LadybirdBrowser ladybird

Truly independent web browser

Stars

65,995

Popular Active

Forks

3,146

Watchers: 65,995

Language

C++

License: BSD 2-Clause "Simplified" License

Repository Radar Score

62 / 100

Growth

7d
+0
30d
+0
%
0.0%

Not enough metric snapshots yet to chart growth for this repository.

Score breakdown

  • popularity 87
  • growth 0
  • activity 100
  • freshness 100
  • community 62

Need help integrating this stack?

Our team builds with modern open-source stacks. Tell us what you are shipping.

Get a quote →

Ladybird

Ladybird is a truly independent web browser, using a novel engine based on web standards.

Important

Ladybird is in a pre-alpha state, and only suitable for use by developers

Features

We aim to build a complete, usable browser for the modern web.

Ladybird uses a multi-process architecture with a main UI process, several WebContent renderer processes, an ImageDecoder process, and a RequestServer process.

Image decoding and network connections are done out of process to be more robust against malicious content. Each tab has its own renderer process, which is sandboxed from the rest of the system.

At the moment, many core library support components are inherited from SerenityOS:

  • LibWeb: Web rendering engine
  • LibJS: JavaScript engine
  • LibWasm: WebAssembly implementation
  • LibCrypto/LibTLS: Cryptography primitives and Transport Layer Security
  • LibHTTP: HTTP/1.1 client
  • LibGfx: 2D Graphics Library, Image Decoding and Rendering
  • LibUnicode: Unicode and locale support
  • LibMedia: Audio and video playback
  • LibCore: Event loop, OS abstraction layer
  • LibIPC: Inter-process communication

How do I build and run this?

See build instructions for information on how to build Ladybird.

Ladybird runs on Linux, macOS, Windows (with WSL2), and many other *Nixes.

How do I read the documentation?

Code-related documentation can be found in the documentation folder.

Get in touch and participate!

Join our Discord server to participate in issue and development discussions.

Please read Getting involved with Ladybird if you're new to Ladybird and want to help.

Before opening an issue, please see the issue policy and the detailed issue-reporting guidelines.

The project participation guidelines can be found in CONTRIBUTING.md.

License

Ladybird is licensed under a 2-clause BSD license.

Created: May 30, 2024

Last push: Sep 3, 2026

Default branch: master

Languages

Share of the codebase by language, based on repository metadata from the host.

  • C++ 45.9%
  • HTML 22.1%
  • Rust 18.1%
  • JavaScript 9.8%
  • Python 1.9%
  • Assembly 0.9%
  • Objective-C++ 0.5%
  • CMake 0.4%
  • CSS 0.2%
  • Shell 0.1%
  • C 0.1%
  • Kotlin 0.0%
  • Objective-C 0.0%
  • WebAssembly 0.0%
  • Dockerfile 0.0%
  • Java 0.0%
  • GLSL 0.0%
  • GDB 0.0%

Repository Radar analysis

Deterministic insights derived from public metadata and our observations — not personal testing or reviews.

Why this repository is interesting

  • High absolute popularity (65,995 stars) signals broad adoption.
  • Maintained recently (last push 2 weeks ago).

Who should use it

  • Developers working primarily with C++

Potential use cases

  • Reference or evaluate C++ open-source approaches in this domain

Strengths

  • Recent repository activity
  • README present in our index
  • Declared license: BSD 2-Clause "Simplified" License
  • Substantial fork count (3,146) suggests reuse and contribution interest

Limitations / considerations

  • Insights are derived from public metadata and our observations — not a substitute for code review

What to watch

  • Re-check last push, issues, and releases on GitHub before production adoption

Strong signals: Strong community interest · Active maintenance

Source: GitHub (public metadata) + Repository Radar analysis. We do not claim ownership of third-party repositories.

Ready to ship something that compounds?

Share your roadmap. We’ll come back with scope options, timeline ranges, and who from Shriram IT Ventures should be in the room.

Popular with product teams