uBO Lite home (MV3)
3.5k
Stars
185
Forks
9
Open issues
8
Contributors
AI Analysis
uBO Lite is a privacy-focused content blocker extension built on the MV3 API, designed for modern browsers (Chrome, Firefox, Edge, Safari). It provides ad and tracker blocking without requiring a persistent background process, making it efficient in terms of CPU and memory usage. It benefits end-users who want to block ads and trackers across multiple browsers while maintaining a lightweight footprint.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
MV3-compliant ad blocker balancing browser compatibility with filtering capability constraints
uBO Lite (uBOL) is a Manifest V3 (MV3) content blocker designed to meet Google Chrome's restrictive extension API requirements while maintaining core ad-blocking functionality. Built by the uBlock Origin maintainers, it uses declarative filtering rules rather than dynamic JavaScript injection, requiring no persistent background process. Available across Chrome, Edge, Firefox, and Safari. Adoption appears substantial but is constrained by MV3's inherent limitations and the continued availability of the more capable uBlock Origin (Manifest V2).
Created September 2022 as MV3 became mandatory. Developed in response to Google's transition away from Manifest V2, which had enabled more sophisticated content filtering. Represents a pragmatic adaptation rather than a preferred redesign; maintains parity with uBlock Origin's default filter lists while accepting reduced JavaScript injection capabilities.
Star growth has been steady but modest (21 stars in 7 days suggests ~3k annualized rate). Adoption likely driven by mandatory browser policy shifts rather than feature superiority. Firefox and Safari releases expanded platform availability. Growth appears correlated with browser enforcement timelines rather than organic preference.
adoption not verified through README, but strong circumstantial evidence: (1) Available on all major browser extension stores (Chrome Web Store, Edge Add-ons, Safari App Store, Firefox releases). (2) Backed by established uBlock Origin maintainers with existing user base migration path. (3) Adoption likely substantial among Chrome users due to MV2 phase-out, but precise download/install numbers not documented in README.
Based on README: operates entirely declaratively via browser-native CSS/JS injection. Service worker remains dormant except during user interaction with popup/options. No permanent filtering process required. Likely implemented as rule-based declarative network request blocking aligned with MV3 Declarative Net Request API. Appears designed to minimize memory footprint and CPU usage compared to Manifest V2 equivalents.
not documented in README
Last push 2026-07-05 (current date 2026-07-06) indicates active maintenance. Repository shows continuous update pattern. Changelog and release notes tracked in wiki. Issue and discussion sections actively managed. Maintenance appears consistent and responsive rather than dormant.
ADOPT IF: you use Chrome, Edge, or Safari and require a lightweight, declarative content blocker that consumes minimal resources; you accept MV3's filtering limitations as a reasonable tradeoff for regulatory compliance. AVOID IF: you need sophisticated dynamic filtering, advanced regex-based rules, or require the full feature set of Manifest V2 extensions; you can continue using uBlock Origin on Firefox where MV2 remains available. MONITOR IF: you are tracking browser policy evolution and extension API maturation; MV3 limitations may ease or worsen depending on regulatory and user pressure.
Independent dimensions
Mainstream potential
4/10
Technical importance
6/10
Adoption evidence
5/10
- MV3 Declarative Net Request API has inherent filtering ceiling (rule count limits, inability to intercept certain request types) that cannot be overcome without browser policy changes. uBOL is constrained by platform, not implementation gaps.
- Dependency on browser vendor goodwill: Google controls Chrome extension ecosystem and can further restrict filtering capabilities. Regulatory pressure could ease or tighten MV3 constraints unpredictably.
- Filter list maintenance burden falls entirely on established maintainers; if uBlock Origin project loses momentum, uBOL filter updates may stall despite active code maintenance.
- User migration from Manifest V2 may face resistance due to perceived capability loss, limiting adoption among power users who remain on Firefox.
- Safari and Firefox adoption may remain niche due to smaller ad-blocker markets on those platforms compared to Chrome ecosystem.
uBOL will remain the official MV3 path for uBlock Origin users and likely achieve modest but stable adoption across major browsers. Mainstream dominance unlikely due to inherent MV3 limitations, but niche adoption as 'best available option under constraints' is probable. Will survive and remain maintained as long as uBlock Origin project remains active.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- JavaScript
- License
- GPL-3.0
- Last updated
- 2d ago
- Created
- 46mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
click2load doesn't allow embed to load on click
Support * wildcards for domains in custom static filters
filtering mode slider inaccessible with screenreaders / keyboard
Can't use zapper or custom filter tools on `whatsapp.com`
Add left/right arrows to decrement/increment by one unit the slider value in "Create custom filter" dialog
Open pull requests
No open pull requests.
Top contributors
Similar repos
uBlockOrigin/uAssets
uAssets is a curated collection of filter lists for uBlock Origin and uBlock...
limbopro/Adblock4limbo
Adblock4limbo is a specialized userscript and configuration tool designed to...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
uBlockOrigin/uBOL-home
this
|
3.5k | +34 | JavaScript | 8/10 | 2d ago |
|
gorhill/uBlock
|
66.1k | — | JavaScript | 10/10 | 22h ago |
|
uBlockOrigin/uAssets
|
5.9k | — | Adblock Filter List | 8/10 | 9h ago |
|
limbopro/Adblock4limbo
|
4.4k | — | JavaScript | 7/10 | 1w ago |
 minbrowser/min
|
9.1k | — | JavaScript | 7/10 | 4d ago |
 iorate/ublacklist
|
6.6k | — | TypeScript | 8/10 | 23h ago |
Original codebase with superior filtering via dynamic JavaScript. Technically more capable but increasingly incompatible with modern browser policies. uBOL is the maintainers' official MV3 response, not a replacement.
Comparable MV3 offering with similar declarative limitations. Less transparent about governance; uBOL maintains stronger community-driven filter lists via uAssets.
Native blocking engine not subject to extension API constraints. Better performance but less user-configurable; targets different architectural layer.
Smaller, community-maintained MV3 blocker. Likely less feature-rich; uBOL benefits from established uBlock Origin ecosystem and filter maintenance.
Privacy-focused blocker with MV3 variant. Broader privacy scope; uBOL remains narrower, ad/tracker focused.