blokadaorg/blokada

The official repo for Blokada apps.

View on GitHub ↗Jump to charts ↓Open shareable report →

blokadaorg/blokada has 3k+ stars and 200+ forks on GitHub, is written in Dart, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on November 19th, 2016
Open Issues & Pull Requests: 207 (+0)
GitHub issues: Enabled
Number of forks: 229
Total Stargazers: 3,268 (+0)
Total Subscribers: 73 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 219.8 days
Mean response time: 371.3 days
90th percentile: 978.3 days
Tracked items: 11

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 832 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • version-5 (2)
  • type-F (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Blokada is a mobile ad blocker and privacy application available for Android and iOS that uses cloud-based DNS filtering to block advertisements and tracking.

The tool addresses unwanted ads and privacy concerns by filtering network traffic at the DNS level rather than on-device. Blokada 6, the current version, operates through a cloud-based adblocking model that requires a subscription to function. This approach differs from Blokada 5, which performs adblocking locally on the device and runs entirely free without requiring a subscription. Both versions are developed independently and coexist as separate offerings.

Developers considering adoption should understand that Blokada 6 targets users willing to pay for enhanced privacy and ad blocking through a subscription model, whereas Blokada 5 suits those preferring free, on-device filtering. The project is written in Dart and distributed through standard app stores. The README emphasizes the importance of downloading from the official website to avoid counterfeit copies and malware sites that impersonate the legitimate application.

The project maintains active community engagement through forums, social media channels, and a developers-only forum for technical discussions. Development issues receive prioritized responses when posted to the designated development forum. The team actively manages an issue tracker and welcomes community contributions, with a dedicated contributing guide available for those interested in participating in development.