Item detail
github.com

vm0-ai/vm0

RepoRadar surfaced vm0-ai/vm0 — a developer tool — into the Radar section, where it sits at Silver tier with a 'watch' verdict. Its strongest signal is practical usefulness, scored 7.6 out of 10.

Score7.6
Popularity30.5
Risknone
TierSilver
Score breakdown
Usefulness7.6
Novelty6.1
Momentum3.5
Maturity6.2
Open-source/build7.4
Evidence7.2
Workflow potential7.6
Setup ease6.5

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

The repo sits in a hot and crowded category (agentic runtimes / Claude Code–style agent harnesses) and has accumulated 1,126 stars and 67 forks in under a year — an unusually fast signal that something here is resonating with developers building computer-use.

Who should use it

Builders Power users

Who should skip it

Skip vm0-ai/vm0 for now if you are only tracking items with a 'try now' verdict.

About this signal

vm0-ai/vm0 is tracked by RepoRadar as a developer tool in the Radar section. It was first seen on 2026-06-12 and last updated on 2026-06-12. The current verdict is 'watch' with a Silver tier and review needed setup difficulty. Across RepoRadar's eight signals, vm0-ai/vm0 is strongest on practical usefulness (7.6) and workflow potential (7.6) and weakest on momentum (3.5) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned vm0-ai/vm0 a composite score of 7.6 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 30.5 and never affects the composite score or tier. The risk label of 'none' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

No inherent user-impacting risk is flagged from the captured evidence.

Evidence links
Closest alternatives / related signals
Verification record

What RepoRadar actually verified

Editorially reviewed

Explicit source-record review against the RepoRadar publication gate. Reviewer: RepoRadar editorial desk. Last checked 2026-07-12T00:00:00Z.

No hands-on run is claimed. This record remains source-reviewed only.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

39 dated snapshots retained from 2026-06-16 through 2026-08-03; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score7.6 current · +0.0 net
Repository momentum9.0 current · +5.5 net
GitHub stars (observed)1,141 current · +5 net
GitHub stars1,141 exact observation
Versionvsock-test-v0.9.181
Last release2026-08-03T08:27:18Z
Maintenanceactive
Current risknone
Current verdictwatch
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineClaude Code

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-037.69.01,141nonewatchactive
2026-08-027.69.01,140nonewatchactive
2026-08-017.69.01,140nonewatchactive
2026-07-317.63.5Not recordednonewatchnot recorded
2026-07-307.63.5Not recordednonewatchnot recorded
2026-07-297.68.51,137nonewatchactive
2026-07-287.69.01,138nonewatchactive
2026-07-217.69.01,137nonewatchactive
2026-07-207.69.01,137nonewatchactive
2026-07-197.69.01,137nonewatchactive
2026-07-187.69.01,137nonewatchactive
2026-07-177.69.01,137nonewatchactive

Why the record changed

stars changed

Stars changed: 1140 → 1141.

version changed

Version changed: runner-rs-v0.151.11 → vsock-test-v0.9.181.

version changed

Version changed: runner-rs-v0.151.8 → runner-rs-v0.151.11.

version changed

Source-observed version changed: runner-rs-v0.151.4 → runner-rs-v0.151.8. Associated release timestamp: 2026-07-31T13:44:05Z → 2026-08-01T10:17:23Z. This reports the retained observation delta and does not infer why the upstream change occurred.

verification changed

Verification changed: Discovered → Editorially reviewed.

version changed

Version changed: runner-rs-v0.148.21 → runner-rs-v0.148.32.

stars changed

Stars changed: 1138 → 1137.

version changed

Source-observed version changed: vsock-test-v0.9.168 → runner-rs-v0.148.21. Associated release timestamp: 2026-07-28T05:55:22Z → 2026-07-28T10:15:56Z. This reports the retained observation delta and does not infer why the upstream change occurred.

version changed

Version changed: runner-rs-v0.146.8 → vsock-test-v0.9.168.

stars changed

Stars changed: 1137 → 1138.

version changed

Source-observed version changed: vsock-test-v0.9.152 → runner-rs-v0.146.8. Associated release timestamp: 2026-07-17T10:07:12Z → 2026-07-17T11:00:45Z. This reports the retained observation delta and does not infer why the upstream change occurred.

version changed

Source-observed version changed: api-v1.283.1 → vsock-test-v0.9.152. Associated release timestamp: 2026-07-17T09:05:34Z → 2026-07-17T10:07:12Z. This reports the retained observation delta and does not infer why the upstream change occurred.