/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

StevenBlack/hosts

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:15:05.473Z

1mo ago

StevenBlack/hosts

StevenBlack/hosts is a very active hosts-file aggregator repository that consolidates curated blocklists into a unified hosts file and publishes many category-based variants. It is large, popular, and recently maintained, with 30k+ stars, 2.3k+ forks, and a release on 2026-03-30.

Loading tags...

Stars30,128

Forks2,399

Default branchmaster

Last pushed2026-03-30T01:33:21Z

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

9 of 9 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if you want its extra category combinations and do not mind falling well behind upstream. Choose upstream if freshness, maintenance, and the widest supported variant set matter more than this fork’s custom recipe focus.

Prefer upstream for almost everyone. This fork is effectively a stale mirror with no added functionality, so adoption only makes sense if you specifically need this repository snapshot.

Prefer this fork only if the extra category mixes are the main requirement. If you want the most current, actively maintained hosts aggregation, upstream is the safer choice.

Choose the upstream project unless you specifically need a frozen legacy fork or want to continue a custom 2018-era branch; this fork is materially behind and should be treated as stale.

Prefer this fork only if you specifically want its older, more expansive category-based blocking setup. For most adopters, upstream is the better choice because it is much newer and actively maintained.

Prefer upstream unless you specifically want an older, unchanged snapshot. This fork adds no visible functionality and is far behind the active project, so it is a poor choice for users who want current block coverage.

Choose this fork only if its older custom variant structure is the point; otherwise upstream is the better default because it is actively maintained and much newer. This fork is for customization and legacy stability, not for staying current.

Prefer upstream unless you explicitly want this fork's older, more customized recipe set. For most adopters, the staleness outweighs the added variants.

Prefer upstream unless you specifically want this fork’s older pinned state and its extra stats/graph workflow; otherwise the maintenance gap is too large for a security/blocklist project.

Fork comparison

mathusiast/hosts

38/100

stale

significant_divergence

Choose this fork if you want its extra category combinations and do not mind falling well behind upstream. Choose upstream if freshness, maintenance, and the widest supported variant set matter more than this fork’s custom recipe focus.

Likely purpose

To provide customized hosts-file recipes with expanded category combinations for stricter content blocking, while preserving the upstream aggregation workflow.

Best for

Users who want a stricter, precomposed hosts file with category mixes like gambling, porn, social, and fakenews blocking.; People who prefer a forked recipe over maintaining their own custom combination.; Adopters who value customization more than staying perfectly current with upstream updates.

Additional features

Extra hosts variants for combined category sets such as fakenews + gambling + porn + social.
More granular recipe permutations for users who want to tune blocking by content category.
A downstream packaging of the same generated-hosts workflow for alternative deployment choices.
Extends or customizes major product areas around `alternates/fakenews-gambling-only/` and `alternates/fakenews-gambling-porn-only/`.

Missing features

It is 255 commits behind upstream, so it likely misses a large number of recent source updates and releases.
Users do not appear to get the very latest upstream blocklist refreshes and bugfixes present in StevenBlack/hosts through 2026-03-30.
Any upstream improvements to generation, testing, or release workflow after the fork point are absent unless manually backported.
It trails upstream by 255 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Useful if you want stronger category-based filtering than the base upstream recipes.
Appears to preserve the core hosts-file aggregation model, so adoption should be straightforward for existing hosts-file users.
The fork already has concrete category combinations that can fit more opinionated filtering policies.

Risks

Being far behind upstream makes the blocklist less current and potentially less effective.
Large divergence increases the chance of stale generated outputs or unbackported fixes.
The fork seems to have low community traction compared with upstream, so long-term maintenance risk is higher.