Discofork
Repository brief

ruvnet/RuView

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-30T11:47:37.727Z
3mo ago

ruvnet/RuView

RuView is an active, non-archived MIT-licensed open source project for WiFi-based human sensing: pose estimation, vital-sign monitoring, and presence detection from CSI data. It appears well-maintained, large in adoption, and currently focused on alpha-stage multi-node sensing and firmware/server fixes.

GitHub
Loading tags...
Stars44,594
Forks5,988
Default branchmain
Last pushed2026-03-30T06:45:38Z
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
Selected

Choose this fork only if you specifically want an older, unchanged RuView baseline. For new adoption, upstream is the better choice because it is active and contains substantial recent multi-node, firmware, and server-side fixes.

Prefer upstream if you want a working WiFi sensing platform. Prefer this fork only if you want the audit/warning narrative and do not need current functionality or documentation.

Prefer upstream RuView unless you specifically need this fork's branding or are starting a new private derivative. This fork is behind by 211 commits and shows no unique code changes, so it adds no clear product value while increasing maintenance risk.

Prefer upstream unless you specifically want this fork's branding or repository identity. The fork shows no concrete functional additions and is far behind upstream, so it is a weaker choice for adopters who need current fixes, active maintenance, or the latest multi-node sensing work.

Prefer upstream unless you specifically need this exact snapshot. This fork does not show added capabilities; it mainly reflects an older, stale copy of RuView.

Prefer upstream for almost everyone. Choose this fork only if you need a pinned, unmodified snapshot of RuView and are willing to backport upstream fixes yourself.

Prefer upstream unless you specifically need this exact older snapshot. This fork does not add capabilities and is materially behind on active sensing, firmware, and server work, so adopters should expect to inherit missed fixes and newer workflows.

Do not adopt this as a maintenance fork unless you specifically need the older upstream snapshot; active users should prefer current upstream because this fork adds nothing and is substantially behind.

Prefer this fork only if you want an almost-stock RuView checkout to branch from. If you want the latest sensing-server, firmware, and multi-node fixes, upstream is the better starting point.

Choose the upstream project instead unless you specifically want a clean, lightly modified mirror to build your own work on top of. This fork does not show added capabilities, and it is behind on recent sensing-server and firmware fixes.