RuView

ruvnet/RuView

π RuView turns commodity WiFi signals into real-time spatial intelligence, vital sign monitoring, and presence detection — all without a single pixel of video.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 12, 2026
today
Ship score
100/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 94,738 → 96,588 (Sep 22 – Oct 6, 2026)
History starts 2026-09-22, the first weekly sample after this repo joined the directory.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
97.4K
Forks
12.8K
Open issues
447
Watchers
871
Primary language
Rust
Created
Jun 7, 2025
Owner
ruvnet · User

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 43 startups in the directory ship primarily in Rust.

Topics

#awesome#claude#densepose#esp32#firmware#home-assistant#home-automation#iot#monitoring#networking#npm#pose-estimation#react#rf#self-learning#skills#spatial-intelligence#typescript#wifi#wifi-security

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 98%, self-hostable 52%, hosted offering 38%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-09-22, found by the weekly discovery job at confidence 0.97. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-12This is the badge for ruvnet/RuView, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/ruvnet/RuView.svg)](https://ossean.com/ruvnet/RuView)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.