Auto-generated — not yet edited · only the numbers are verified
- TESIGN / RADAR
- REPOSITORY CARD
- ladybirdbrowser/ladybird
ladybirdbrowser/ladybird
Truly independent web browser
RANKS All-time #86
AT A GLANCE
- LANGUAGE
- C++
- LICENSE
- BSD-2-Clause
- USAGE
- Use, change and redistribute, commercially too. Keep the notice.
- ACTIVITY
- last commit 3 days ago ()
- TOPICS
- browser
- browser-engine
- HOMEPAGE
- https://ladybird.org
- REPOSITORY
- GitHub ↗
A summary, not legal advice.
README EXCERPT
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 Lady…
The opening of the GitHub README as stored, at most 1,200 characters. Markdown is not rendered.
TIMELINE
- Repository created
- FIRST SEEN BY TESIGN ◌ BACK CATALOG
- Last push
AI chooses the lists under the owner’s delegation. No human review is running in September 2026. Total stars, increases, cross-source signals, last updates and licences are shown as evidence. How ranks work →
If this repository gets editorial text (why, build, who, start, caveat) it becomes an edited entry. Until then the page shows only stored GitHub metadata and numbers.