Trending repositories

Ranked by Attention Score: stars gained over the last 90 complete days

Period

Sort order

Tags: DNS

1.jeessy2 / ddns-go

Simple and easy to use DDNS. Support Aliyun, Tencent Cloud, Dnspod, Cloudflare, Callback, Huawei Cloud, Baidu Cloud, Porkbun, GoDaddy, Namecheap, NameSilo...

ddns
alidns
dnspod
cloudflare
baiduyun
porkbun
+1 more

Go MIT18K total1.9K forks

+420 stars

from 17,103 · score 6.04

2.DNSCrypt / dnscrypt-proxy

dnscrypt-proxy 2 - A flexible DNS proxy, with support for encrypted DNS protocols.

dnscrypt
dnscrypt-proxy2
doh
dnscrypt-proxy
dns-over-https
dns
+6 more

Go ISC14K total1.1K forks

+311 stars

from 13,496 · score 5.74

3.0xERR0R / blocky

Fast and lightweight DNS proxy as ad-blocker for local network with many features

ad-blocker
adblocker
dns
self-hosted
golang
selfhosted
+5 more

Go APACHE-2.07.1K total319 forks

+281 stars

from 6,809 · score 5.64

4.coredns / coredns

CoreDNS is a DNS server that chains plugins

dns-server
go
cncf
coredns
plugin
service-discovery

Go APACHE-2.014K total2.6K forks

+214 stars

from 14,195 · score 5.37

5.miekg / dns

DNS library in Go

dnssec
go
dns-library
dns

Go BSD-3-CLAUSE8.8K total1.2K forks

+71 stars

from 8,730 · score 4.28

6.hashicorp / mdns

Simple mDNS client/server library in Golang

Go MIT1.4K total226 forks

+27 stars

from 1,369 · score 3.33

7.semihalev / sdns

A high-performance, recursive DNS resolver server with DNSSEC support, focused on preserving privacy.

dns
dns-server
dnssec
dns-resolver
edns
dns-over-https
+4 more

Go MIT1.1K total74 forks

+21 stars

from 1,068 · score 3.09

8.TimothyYe / godns

A dynamic DNS client tool that supports AliDNS, Cloudflare, Google Domains, DNSPod, HE.net & DuckDNS & DreamHost, etc, written in Go.

dns
dnspod
ddns
dyndns
dynamic-dns
duckdns
+5 more

Go APACHE-2.01.8K total248 forks

+17 stars

from 1,769 · score 2.89

Order: Attention Score

Most net stars gained in the window first. The score only puts this gain on a log scale, so the order is the order of the gain.

How the ranking works

Ranked by stars gained in the window. The score is the natural log of one plus that gain, so a repository's rank is exactly its star gain's rank.

score = log1p(net stars gained in the trailing T complete UTC days)

A repository is ranked only when its Star History covers every day of the window and its latest Observation is not missing.

The longest window is 180 days. Star History from the Repository Host goes back at most 180 days before the first daily record that AwesomeRepos made for the repository. A longer window needs more of these daily records first. A repository younger than the window does not rank in it.

The filters select from the same eligible repositories. A repository matches the topics when it has any of them. Total stars is the count now. Last push and creation on the Repository Host count back from the start of today (UTC). The counts beside the languages, licenses, and topics include all ranked repositories in the window. A Tag holds the repositories that have it. See Tags.

A new repository enters the index when it gains stars faster than the published admission threshold, whatever its size. A repository stays in the index after it enters. Thus an archived repository can still rank.

Browse the Repository Index