Trending repositories

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

Period

Sort order

Tag

Filters (1)

Apply

Filters

Primary language

License

Total stars

Last push

Created

Archived

Clear all filters

6 repositories by Attention Score · Oct 28, 2026 – Nov 3, 2026 (UTC)

Language: Rust
Tag: Remote desktop
Clear all

1.rustdesk / rustdesk

An open-source remote desktop application designed for self-hosting, as an alternative to TeamViewer.

remote-control
remote-desktop
teamviewer
anydesk
vnc
rdp
+13 more

Rust AGPL-3.0128K total20K forks

+771 stars

from 127,295 · score 6.65

2.Ntarasiuk / glass

Low-latency remote desktop for macOS and Linux. Control your computer from an iPad or any browser with ~20 ms delay. Free, open source, no app to install. curl -fsSL glassdesk.dev | sh

ipad
macos
remote-desktop
rust
screen-sharing
tailscale
+14 more

Rust MIT169 total12 forks

+168 stars

from 1 · score 5.13

3.VallierDev / uu-remote-linux

TranslatedUnofficial Linux host for NetEase UU Remote

Rust GPL-3.0618 total254 forks

+140 stars

from 478 · score 4.95

4.rustdesk / rustdesk-server

RustDesk Server Program

remote-desktop
remote-control
remote-access
tauri

Rust AGPL-3.011K total2.7K forks

+40 stars

from 10,625 · score 3.71

5.warp-tech / warpgate

Fully transparent SSH, HTTPS, Kubernetes, database and RDP/VNC bastion/PAM that doesn't need additional client-side software

bastion
bastion-host
infrastructure
ssh
ssh-server
proxy
+14 more

Rust APACHE-2.08.2K total438 forks

+38 stars

from 8,158 · score 3.66

6.LumaryLabsLLC / muxin

All your machines, one app. For you and your AI agents: agent sessions, desktops, files, logs and GitHub across your Macs, Linux and Windows machines, with an MCP server.

ai-agents
claude-code
devtools
gpui
mcp
remote-desktop
+4 more

Rust APACHE-2.0388 total58 forks

+12 stars

from 376 · score 2.56

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.

Repositories enter the index from the starting dataset of the index, or by gaining stars faster than the published admission threshold, whatever their size. A repository stays in the index after it enters. Thus an archived repository can still rank.

Browse the Repository Index