/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

AdguardTeam/AdGuardHome

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T16:01:59.952Z

1mo ago

AdguardTeam/AdGuardHome

AdGuardHome is an actively maintained Go-based, network-wide DNS blocking server for ads and trackers. It appears mature and widely adopted, with 33,325 stars, 2,285 forks, and recent commits on 2026-03-30. Forks are likely most interesting if you want to build on a privacy/DNS filtering product with a substantial existing codebase and active upstream churn.

Loading tags...

Stars33,325

Forks2,285

Default branchmaster

Last pushed2026-03-30T09:02:20Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if you specifically need its older customizations and are prepared to maintain a large downstream delta. For most adopters, upstream is the safer choice because this fork is stale and materially behind current development.

Prefer upstream unless you specifically need this older snapshot; this fork adds no visible capabilities and is materially behind on maintenance.

Choose this fork only if you specifically need its customizations and are willing to own maintenance. For most adopters, upstream is the safer choice because this fork is stale and materially behind current development.

Choose this fork if you value its custom tracker-data and workflow/UI changes more than upstream compatibility. Avoid it if you want the easiest path to current AdGuard Home releases, because the branch is already significantly behind and far enough ahead to imply real divergence.

Choose this fork only if Windows 7 support or the bundled Windows launcher matters more than staying close to upstream. For most users, upstream is the safer default because this fork is materially behind and appears to strip documentation.

Prefer upstream AdGuardHome unless you need this exact older snapshot. This fork does not add meaningful capabilities and is materially behind current upstream, so it is a poor choice for adopters seeking improvements or extra workflows.

Choose this fork if alert-only monitoring is the main feature you want. Choose upstream if you want current maintenance, broad compatibility, and the lowest operational risk.

Choose this fork only if its downstream behavior is exactly what you need and you are prepared to own future maintenance. For most adopters, upstream is the safer default because this fork is stale and materially behind.

Prefer upstream unless you specifically need this older customized baseline. This fork is best for legacy or bespoke deployments, not for users who want current fixes, active maintenance, or low-risk adoption.

Choose this fork only if you specifically need its old customized state. For most adopters, upstream AdGuardHome is the better default because this fork is very stale and far behind current development.

Fork comparison

ashu1230/AdGuardHome

38/100

stale

significant_divergence

Choose this fork only if you specifically need its older customizations and are prepared to maintain a large downstream delta. For most adopters, upstream is the safer choice because this fork is stale and materially behind current development.

Likely purpose

A heavily customized older snapshot of AdGuard Home, likely used to experiment with UI, filtering data, and internal behavior rather than to stay current with upstream.

Best for

Operators who want a frozen, customized AdGuard Home variant and do not need current upstream changes.; Teams willing to own their own maintenance and merge upstream fixes manually.; Developers experimenting with filtering data, UI tweaks, or internal behavior changes on top of an older base.

Additional features

Custom tracker-list data and related client filtering assets, including a large replacement of tracker metadata files.
Client-side UI and locale work, with substantial changes under `client/src/__locales*` and `client/src/components/ui/`.
Operational and service-list behavior changes in `internal/filtering/servicelist.go` and `internal/home/home.go`.
Packaging/build-system drift via new or changed lockfiles and build-related files such as `client2/yarn.lock` and `openapi/yarn.lock`.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

The fork is far behind upstream, with 299 commits behind and no pushes since 2022-12-23, so it likely lacks many upstream fixes and features from 2023-2026.
Upstream currently has active development on DNS-over-HTTPS, dnsproxy integration, launchd/service status, and packaging fixes that this fork likely does not include.
Tests and internal migration coverage appear reduced in places, with large deletions in `internal/configmigrate/migrations_internal_test.go`, `internal/dnsforward/dnsforward_internal_test.go`, and `internal/client/storage_test.go`.
The fork appears to have pruned or replaced upstream tracker data rather than tracking upstream’s current lists and related behavior.
It trails upstream by 299 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Large customization surface for clients that want to control filtering data or UI behavior.
May suit operators maintaining an older, stable internal variant with their own local changes.
Substantial code coverage across Go, web client, and packaging layers, so it is not a trivial patch fork.

Risks

Very stale relative to upstream, which raises security, compatibility, and maintenance risk.
Large divergence makes rebasing or adopting upstream fixes expensive.
Changed or removed tests increase the chance of regressions being missed.
The fork may be harder to support because the edit set spans many areas without recent activity.

AdguardTeam/AdGuardHome · Discofork