LMDeploy helps developers compress and deploy large language models for practical inference and serving workflows.
Scores
The two headline scores, measured daily, with 30, 90, and 180 day views.
Jul 19, 2026
Current23
Previous30
Weekly average
Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.
180 observed daily rows. Missing days are not fabricated.
40% Hot today + 40% Hot this week + 20% Breakout.
Per-day formula: 0.40 × Hot today + 0.40 × Hot week + 0.20 × Breakout.
| Date | Stars | Stars 1d | Stars 7d | Stars 14d | Stars 30d | Stars 90d | Same-day multiplier | Weekly multiplier | Fortnight multiplier | Hot today | Hot week | Breakout | Stored score |
|---|
Jul 19, 2026
Current70
Previous70
Weekly average
Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.
180 observed daily rows. Missing days are not fabricated.
30% Continuity + 30% Closure + 20% Shipping + 10% Liveness + 10% Support burden.
Per-day formula: 0.30 × Continuity + 0.30 × Closure + 0.20 × Shipping + 0.10 × Liveness + 0.10 × Support burden.
Stars, issues, pull requests, and releases are daily observations. Pushed-days and license are repository snapshot-derived inputs and are not independent historical GitHub events.
| Date | Issues opened | Issues closed | PRs opened | PRs merged | Releases | Stars | Open issues | Pushed days ago | Continuity | Closure | Shipping | Liveness | Support burden | License | Observed days | Missing days | Needs healing | Stored score |
|---|
Reliability breakdown
Component scores measured daily from GitHub activity (2026-07-18).
Activity on 4 of 90 tracked days in the last 90 and 1 of 30 in the last 30.
Merged 0 of 0 PRs opened and closed 0 of 0 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.
8 releases in the last 180 days, 4 in the last 90 and 1 in the last 30 — a steady cadence scores highest.
Last push 3 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).
Modeled — lower is better; concentration of commits in few maintainers. Contributors graph
Topics
Jump into the topic listings this repository belongs to.
Measured history
Weekly GitHub totals with 30, 90, and 180 day views.
Mar 8, 2026
Current1
Previous7
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
46 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Mar 8, 2026
Current3
Previous7
Weekly total
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
46 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Mar 8, 2026
Current14
Previous13
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
46 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Mar 8, 2026
Current13
Previous18
Weekly total
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
46 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Mar 8, 2026
Current11
Previous16
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
46 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Mar 2, 2026
Current2.00
Previous0.00
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is issues closed that day ÷ issues opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more issues than arrived that day.
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
20 observed daily rows. Missing days are not fabricated.
Per-day formula: issues closed that day ÷ issues opened that day; blank when nothing was opened (a gap, not a zero).
| Date | Issues opened | Issues closed | Stored score |
|---|
Mar 6, 2026
Current0.50
Previous1.00
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is pull requests closed that day ÷ pull requests opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more pull requests than arrived that day.
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
27 observed daily rows. Missing days are not fabricated.
Per-day formula: pull requests closed that day ÷ pull requests opened that day; blank when nothing was opened (a gap, not a zero).
| Date | PRs opened | PRs closed | Stored score |
|---|
Jul 19, 2026
Current0
Previous0
Weekly total
GitHub release published_at events bucketed by UTC day; drafts are excluded.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
LMDeploy is designed for teams that need to take large language models from raw weights to deployable services. Its scope spans compression, deployment, and serving, which makes it relevant for production environments where runtime efficiency matters as much as model capability. For engineering teams evaluating model serving infrastructure in the LLM stack, LMDeploy is a focused open source option centered on operational delivery.
Join the conversation
Share what you know about lmdeploy — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Explain what worked, what broke down, and what another team should know before adopting lmdeploy.
Project Q&A
Browse implementation threads tied directly to InternLM/lmdeploy. Each question links through to the full answer page.
Be the first to ask how teams run lmdeploy in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses lmdeploy — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post