Skip to report

Independent analytics for a public GitHub repository

vitejs/vite

Next generation frontend tooling. It's fast! — view on GitHub · vite.dev · npm: vite

Language

TypeScript

License

MIT

open source

Created

Apr 2020

Stars

82,926

Forks

8,760

Issues

510 open

Updated 21 Sept 2026, 03:34 UTC

86 /100
ACTIVELY MAINTAINED

tracker score 86/100 methodology →

Computed from release cadence, responsiveness, backlog trend and contributor depth.

Last release

11 days ago

v8.3.0

Cadence

bursty, <1d median

11d gap

PR merge median

1.2d

Issue response median

15.5h

Commits / 7d

17

560 points on Hacker News — “Vite 8.0 Is Out” source →

Attention vs delivery — is popularity translating into shipping?

The signature question of dependency due diligence. Columns: npm downloads per month (attention). Line: merged pull requests per month (delivery). 12 full months.

attention — npm downloads / month delivery — merged PRs / month stable release

Reading: npm downloads grew 10.4× over 24 months while delivery held at ~86 merged PRs/mo. No divergence risk — delivery tracks attention.

Star-spike forensics — why did this repo blow up, and when?

Star-velocity anomalies cross-referenced with Hacker News, Reddit and release events.

234 points on Hacker News — “Vite+ Beta” source →

179 points on Hacker News — “The Rust React Compiler is now native in Vite” source →

109 points on Hacker News — “Vite+ – Unified toolchain for the web” source →

Responsiveness — vs cohort percentiles

How fast maintainers answer, review and merge — ranked against repos of similar size and age.

Issue first non-author response

median 15.5hcohort: n/a

PR first review

median 22.3hcohort: n/a

PR merge time

median 1.2dcohort: n/a

Bots excluded Sample: 323 merged PRs (90d) / 39 recent issues. Percentile position measured from the left — shorter is faster.

First-contributor funnel — what happens to a newcomer’s PR?

25

first-time PRs (12 mo)

60%

got a response

n=438 scanned

0%

were merged

118 newcomer candidates

20%

returned ≤90d

verified via author history

Verdict: tough room for newcomers — only 60% of verified first-time PRs got a maintainer-class response and 0% merged (window 2026-03-25..2026-06-23). The core team ships fast, but drive-by PRs mostly sit open.

Contributor concentration (12 mo)

top 1 — 60.9% of accepted changes · last commit Sep 13

top 3 — 76.6% of accepted changes

long tail — 31 further authors

Verdict: high key-person risk. 34 human commit authors in 12 months; top author (sapphi-red) holds 60.9%, top 3 hold 76.6%, 9 authors above 1% each.

Open-issue backlog

Open issues and pull requests right now. Trend history builds from daily tracking.

open issues & PRs — right now

510

open issues

283

open pull requests

Tracking daily since 27 Aug 2026 — 20 snapshots so far.

793 open

510 issues + 283 PRs · backlog up 3% over 25d

Fork network & successors

8,760 forks · 0 with independent momentum

vitejs/rolldown-vite — 1,264★ · last push 201d ago

stale

vitejs/vite is upstream — no successor needed (project active). Top forks by stars are all stale (pushes >1y ago). Successor detection activates if the repo goes dormant.

If this repo goes dormant, this section becomes “Where did development continue?” — with evidence labels per fork.

What changed — last 90d

21 stable releases in 90d (median gap 0.9d)

Issue response sits at a 15.5h median — up from 2.4h 25d ago

License unchanged · not archived · no rename/transfer

Max release gap in 12mo: 33d (cadence 0.9d median)

Frequently asked answered from live data · FAQPage structured data

These answers regenerate on every snapshot — they never rot.

Is vite still maintained?

Yes — actively (score 86/100). Last stable release v8.3.0 11 days ago, 17 commits in the last full week, median PR merge 1.2d. Evidence collected Mon Sep 21 2026.

What license does vite use?

MIT — as reported by GitHub.

When was the last vite release?

v8.3.0, 11 days ago. Median gap between stable releases is 0.9 days; 21 stable releases shipped in the last 90 days — the current 11d gap is well above that median.

Is vite safe to adopt for a new project in 2026?

On the evidence: yes. 132.0M npm downloads/week, 2,381 dependents on the default version, 34 human authors, 0 advisories on the current default, no fork-succession pressure. Caveat for contributors: the newcomer funnel is weak (0% first-PR merge rate).

Share & embed — every share is a branded mini-report

Link preview (auto-generated OG card)

tracker.git.tools

vitejs/vite

ACTIVELY MAINTAINED · 86/100

ships bursty, <1d median · PR merge 1.2d · ★ 82,926 (npm +944%/24mo)

vitejs/vite — maintenance verdict & repo intelligence · tracker.git.tools

README badge (live SVG — every embed is a backlink)

maintenance active · 86
[![maintenance](https://tracker.git.tools/badge/vitejs/vite)](https://tracker.git.tools/vitejs/vite)

Badge states: active · slowing · maintenance-only · dormant — flips automatically; maintainers embed it because it’s honest.

Methodology

Built from the public GitHub API, the npm registry, deps.dev and Hacker News. Known bot accounts are excluded from response and merge metrics. Verdicts are computed from the evidence shown on this page — nothing is scored that you cannot see. Reports refresh daily.