Item detail
github.com

qualcomm/GenieX

qualcomm/GenieX is a model release in RepoRadar's Local AI section, holding Gold tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 9.8 out of 10.

Score8.7
Popularity46.0
Riskconditional
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum8.0
Maturity7.7
Open-source/build8.4
Evidence8.0
Workflow potential9.8
Setup ease6.4

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

Why it matters

Useful for builders who want one vendor-backed path for local AI on Qualcomm hardware instead of stitching together separate edge, Android, and desktop inference stacks by hand.

Who should use it

Developers building local AI apps for Snapdragon X Windows PCs Android teams that want an official on-device LLM or VLM runtime instead of a one-off research port Edge and embedded builders comparing Qualcomm acceleration against other local inference stacks Teams that need a local OpenAI-compatible endpoint on supported Qualcomm hardware

Who should skip it

Pass on qualcomm/GenieX if its scope or audience does not match what your team is building right now.

About this signal

qualcomm/GenieX is tracked by RepoRadar as a model release in the Local AI section. First seen 2026-06-27; the source record was last checked on 2026-06-27. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. qualcomm/GenieX leads on workflow potential (9.8) and practical usefulness (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The qualcomm/GenieX record combines a 8.7/10 composite score with separate popularity (46.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read Local AI vs. hosted APIs: how to choose for the checklist behind this score.

Risk explanation

Peak performance depends on supported Qualcomm NPUs and vendor-specific acceleration paths, so validate your exact hardware before you commit to it as a cross-device runtime standard; The OpenAI-compatible local server is convenient for app testing but should be bound and exposed carefully so a local model endpoint does not become an accidental network service; Model bring-up still varies between raw GGUF weights and Qualcomm AI Hub bundles, so treat compatibility testing as real evaluation work rather than a one-click promise.

Evidence links
Closest alternatives / related signals
local-ai inference qualcomm snapdragon android windows-arm openai-compatible bsd-3-clause
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

38 dated snapshots retained from 2026-06-27 through 2026-08-13; 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 score8.7 current · +0.0 net
Repository momentum9.0 current · +1.0 net
GitHub stars (observed)8,304 current · +104 net
GitHub stars8,304 exact observation
Versionv0.3.19
Last release2026-08-07T18:25:01Z
Maintenanceactive
Current riskconditional
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.79.08,304conditionaltry nowactive
2026-08-128.78.58,304conditionaltry nowactive
2026-08-118.78.58,305conditionaltry nowactive
2026-08-108.79.38,313conditionaltry nowactive
2026-08-098.79.38,310conditionaltry nowactive
2026-08-088.79.38,308conditionaltry nowactive
2026-08-078.79.08,294conditionaltry nowactive
2026-08-068.78.0Not recordedconditionaltry nownot recorded
2026-08-058.78.0Not recordedconditionaltry nownot recorded
2026-08-048.79.08,294conditionaltry nowactive
2026-08-038.79.08,294conditionaltry nowactive
2026-08-028.79.08,293conditionaltry nowactive

Why the record changed

stars changed

Stars changed: 8305 → 8304.

stars changed

Stars changed: 8313 → 8305.

stars changed

Stars changed: 8310 → 8313.

stars changed

Stars changed: 8308 → 8310.

version changed

Version changed: v0.3.18 → v0.3.19.

stars changed

Stars changed: 8294 → 8308.

stars changed

Stars changed: 8293 → 8294.

stars changed

Stars changed: 8292 → 8293.

stars changed

Source-observed stars changed: 8291 → 8292. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 8272 → 8277.

version changed

Version changed: v0.3.14 → v0.3.17.

stars changed

Stars changed: 8230 → 8272.