syv-ai/HyperQwen

Serve large Qwen models fast on the GPUs you actually own. Qwen3.8-27B on a single 24 GB card with vLLM: 127 tok/s single-user (381 when the answer quotes the prompt), ~1,035 tok/s at 64 concurrent, 150k-262k context. vLLM patches, requant pipeline, benchmarks.

2k stars · 277 forks · Python

Healthy

Healthy: actively maintained by 29 people, no known risks.

Why

No rule fired.

What would change this

Maintenance

Complete

Active

Human commits, 30 days
176
Human commits, 90 days
491
Human commits, 365 days
491
Bot share of commits, 365 days
0%
Last commit
Oct 11, 2026 (3 days ago)
Last human commit
Oct 11, 2026 (3 days ago)
Authors, 90 days
29
Last release
none found
Median PR merge time
23 hours

Responsiveness: of 22 recent issues, 95% got a maintainer reply. Median first response: 13 hours.

Sources: Commits, Releases, Merged pull requests, Issues

People

Complete
Owner
Organization
Commits sampled
491 since Oct 15, 2025
Authors for half of commits
2
Authors for 80% of commits
3
Contributors
27

Top committers

Sources: Commits, Contributors

Stars

Complete

Not enough data, confidence medium

Stars per week, 2026-08-09 to 2026-10-11. 0 weeks overlap a burst.Peak 442 a week2026-08-092026-10-11
Bars show stars gained each week. Orange bars overlap a burst.

Anyone can buy stars for any repo; bursts alone don't prove the owner did.

Sources: How star history is analyzed

Risk

Complete

Flags

No risk flags.

License

Now
Apache-2.0 (OSI-approved)
A year ago
Not known

Packages

No published packages found.

Sources: GitHub: syv-ai/HyperQwen

Badge

Add this to a README to show the current verdict:

[![RepoRadar](https://reporadar.ai/syv-ai/HyperQwen/badge.svg)](https://reporadar.ai/syv-ai/HyperQwen)

Earlier verdicts

Computed 2 hours ago · method 2026.10.2