vuejs/core

πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

53,998
Stars
about 8 years
Age
0
Published reviews
0
Questions

Reliability breakdown

What drives the reliability score

Component scores measured daily from GitHub activity (2026-07-15).

Continuity30% of headline79

Activity on 80 of 90 tracked days in the last 90 and 25 of 30 in the last 30.

Closure30% of headline84

Merged 193 of 269 PRs opened and closed 119 of 44 issues opened over the last 90 tracked days β€” PR flow carries 55% of this component, issue flow 45%.

Shipping20% of headline100

27 releases in the last 180 days, 15 in the last 90 and 4 in the last 30 β€” a steady cadence scores highest.

Liveness10% of headline100

Last push 0 days ago β€” freshness decays as pushes age (roughly halves every 83 days without a push).

Support burden10% of headline79

566 open issues against 53,998 stars β€” about 10 open issues per 1,000 stars. Lighter backlogs score higher.

Adoption confidence100

Modeled β€” how confidently teams are adopting this repo. Stargazers

Maintenance quality88

Modeled from PR/issue responsiveness and upkeep signals. Activity pulse

Risk score12

Modeled β€” lower is better; adoption and continuity risk. Repository

Stays active (30d)84%

Modeled chance the repo stays active over 30 days. Activity pulse

Stays active (90d)91%

Modeled chance the repo stays active over 90 days. Activity pulse

Release rhythm (180d)100

Regularity of releases over the last 180 days. Releases

Maintainer bus risk (90d)16%

Modeled β€” lower is better; concentration of commits in few maintainers. Contributors graph

1) Project Overview

Vue is the core repository for the Vue 3 framework, focused on building interactive web interfaces with a reactive data model and component-based structure. You use it when your team wants a framework that stays approachable for small screens and scales into larger frontends without forcing a single architectural style.

In practice, you get a runtime, a template compiler, and APIs such as the Composition API. You can start with simple component rendering and progressively add routing, state patterns, SSR, or static generation through companion tooling.

If your team needs strict long-term predictability, Vue core is mature and actively maintained, but you still need to standardize conventions early so features do not drift across components.

2) Key Challenges Addressed

You usually run into a few recurring frontend problems: state updates spreading unpredictably, component logic becoming hard to reuse, and rendering performance degrading as screens grow.

  • Vue’s reactivity system tracks dependencies and updates only the affected UI paths.
  • Composition API lets your team package logic into composables so behavior stays reusable across components.
  • Computed values and watchers let you separate derived state from side effects.
  • Template compilation and runtime patching reduce manual DOM work while preserving control where needed.

You also avoid heavy boilerplate for many common screens, which lowers friction when your team iterates quickly.

3) Getting Started

You can scaffold a Vue app with the official create flow, then build a first interactive screen with the vue package.

npm create vue@latest
cd your-app
npm install
npm run dev

A minimal component-state pattern in JavaScript looks like this:

import { createApp, ref } from 'vue'

const App = {
  setup() {
    const count = ref(0)
    function increment() {
      count.value += 1
    }
    return { count, increment }
  }
}

createApp(App).mount('#app')

Sharp edges you should plan for immediately:

  • Decide early between Options API and Composition API as your default style.
  • Define one state strategy for cross-component data before feature count grows.
  • Lock linting and formatting conventions so composables and components stay uniform.

4) Features and Use Cases

Vue core supports a broad set of product patterns when your team needs progressive complexity.

  • Reactive forms and dashboards with computed state and watchers.
  • Component libraries with props, emits, slots, and scoped styling patterns.
  • Content-heavy pages with hydration or SSR through ecosystem tooling.
  • Incremental adoption in existing pages where you mount Vue on selected DOM islands.

For UI composition, single-file components keep template, logic, and style close together, while composables keep shared behavior modular.

5) Ecosystem and Dependencies

Vue core plugs into a strong toolchain. You often pair it with Vite for local development and builds, Vue Router for route state, and Pinia for store patterns. For SSR or full-stack patterns, Nuxt is a common path.

What your team gains from this ecosystem is operational consistency: fast local feedback loops, standard conventions for routing and state, and a clear migration path from SPA to SSR when product requirements change.

6) Architectural Overview

Vue core is organized around renderer internals, a reactive dependency-tracking system, and compile-time optimizations for templates. Your components declare state and UI shape, and the runtime coordinates updates through tracked dependencies.

Key design implications for your team:

  • Performance: dependency tracking reduces unnecessary re-renders when state changes.
  • Extensibility: composables and plugin patterns keep cross-cutting concerns modular.
  • Operability: SSR and hydration paths let you tune time-to-content and runtime interactivity.
  • Upgrades: a stable core API and migration tooling reduce risk when you move across minor versions.

7) Pros and Cons

  • Pro: Fast onboarding for teams that want readable templates and gradual complexity.
  • Pro: Strong balance between ergonomic APIs and runtime performance.
  • Pro: Clear ecosystem around routing, state, and modern build tooling.
  • Con: Style divergence appears quickly if your team does not standardize API usage.
  • Con: Large codebases still need disciplined architectural boundaries; framework defaults alone do not enforce them.
  • Con: SSR and advanced rendering paths add operational complexity that needs early ownership.

8) Comparison and Alternatives

Measured 90-day trends for this project and its alternatives.

GitHub stars

Weekly star gains

380185-9
Full metrics details

GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.

Core

GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
React

GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Angular

GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Svelte

GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Preact

GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Solid

GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.

180 observed daily rows. Missing days are not fabricated.

DateValue

Issues opened

Weekly total

36180
Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

Core

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
React

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Angular

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Svelte

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Preact

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Solid

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue

Issues closed

Weekly total

73370
Full metrics details

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

Core

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue
React

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue
Angular

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue
Svelte

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue
Preact

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue
Solid

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests opened

Weekly total

162810
Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

Core

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
React

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Angular

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Svelte

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Preact

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Solid

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests closed

Weekly total

142710
Full metrics details

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

Core

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue
React

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue
Angular

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue
Svelte

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue
Preact

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue
Solid

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

175 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests merged

Weekly total

115580
Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

Core

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
React

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Angular

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Svelte

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Preact

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue
Solid

GitHub API observation. Historical values render only when the source provides a real observation for that day.

175 observed daily rows. Missing days are not fabricated.

DateValue

Open/closed pull request ratio

Weekly average

100500
Full metrics details

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

Core

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
React

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Angular

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Svelte

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Preact

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Solid

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue

Open/closed issues ratio

Weekly average

100500
Full metrics details

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

Core

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
React

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Angular

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Svelte

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Preact

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue
Solid

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

180 observed daily rows. Missing days are not fabricated.

DateValue

Releases

Weekly total

740
Full metrics details

GitHub release published_at events bucketed by UTC day; drafts are excluded.

Core

GitHub release published_at events bucketed by UTC day; drafts are excluded.

180 observed daily rows. Missing days are not fabricated.

DateValue
React

GitHub release published_at events bucketed by UTC day; drafts are excluded.

180 observed daily rows. Missing days are not fabricated.

DateValue
Angular

GitHub release published_at events bucketed by UTC day; drafts are excluded.

180 observed daily rows. Missing days are not fabricated.

DateValue
Svelte

GitHub release published_at events bucketed by UTC day; drafts are excluded.

180 observed daily rows. Missing days are not fabricated.

DateValue
Preact

GitHub release published_at events bucketed by UTC day; drafts are excluded.

180 observed daily rows. Missing days are not fabricated.

DateValue
Solid

GitHub release published_at events bucketed by UTC day; drafts are excluded.

180 observed daily rows. Missing days are not fabricated.

DateValue

Hotness score

Weekly average

100500
Full metrics details

Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.

Core

Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.40 Γ— Hot today + 0.40 Γ— Hot week + 0.20 Γ— Breakout.

  • Same-day multiplier = stars 1d Γ· max(1, stars 7d Γ· 7)
  • Weekly multiplier = stars 7d Γ· max(1, stars 30d Γ· 30 Γ— 7)
  • Fortnight multiplier = stars 14d Γ· max(1, stars 90d Γ· 90 Γ— 14)
  • Hot today = clamp(70 Γ— log-scale(stars 1d, 1000) + 30 Γ— breakout-scale(same-day, 4))
  • Hot week = clamp(75 Γ— log-scale(stars 7d, 5000) + 25 Γ— breakout-scale(weekly, 3))
  • Breakout = clamp(35 Γ— breakout-scale(same-day, 4) + 40 Γ— breakout-scale(weekly, 3) + 25 Γ— breakout-scale(fortnight, 2.5))
DateStarsStars 1dStars 7dStars 14dStars 30dStars 90dSame-day multiplierWeekly multiplierFortnight multiplierHot todayHot weekBreakoutStored score
React

Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.40 Γ— Hot today + 0.40 Γ— Hot week + 0.20 Γ— Breakout.

  • Same-day multiplier = stars 1d Γ· max(1, stars 7d Γ· 7)
  • Weekly multiplier = stars 7d Γ· max(1, stars 30d Γ· 30 Γ— 7)
  • Fortnight multiplier = stars 14d Γ· max(1, stars 90d Γ· 90 Γ— 14)
  • Hot today = clamp(70 Γ— log-scale(stars 1d, 1000) + 30 Γ— breakout-scale(same-day, 4))
  • Hot week = clamp(75 Γ— log-scale(stars 7d, 5000) + 25 Γ— breakout-scale(weekly, 3))
  • Breakout = clamp(35 Γ— breakout-scale(same-day, 4) + 40 Γ— breakout-scale(weekly, 3) + 25 Γ— breakout-scale(fortnight, 2.5))
DateStarsStars 1dStars 7dStars 14dStars 30dStars 90dSame-day multiplierWeekly multiplierFortnight multiplierHot todayHot weekBreakoutStored score
Angular

Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.40 Γ— Hot today + 0.40 Γ— Hot week + 0.20 Γ— Breakout.

  • Same-day multiplier = stars 1d Γ· max(1, stars 7d Γ· 7)
  • Weekly multiplier = stars 7d Γ· max(1, stars 30d Γ· 30 Γ— 7)
  • Fortnight multiplier = stars 14d Γ· max(1, stars 90d Γ· 90 Γ— 14)
  • Hot today = clamp(70 Γ— log-scale(stars 1d, 1000) + 30 Γ— breakout-scale(same-day, 4))
  • Hot week = clamp(75 Γ— log-scale(stars 7d, 5000) + 25 Γ— breakout-scale(weekly, 3))
  • Breakout = clamp(35 Γ— breakout-scale(same-day, 4) + 40 Γ— breakout-scale(weekly, 3) + 25 Γ— breakout-scale(fortnight, 2.5))
DateStarsStars 1dStars 7dStars 14dStars 30dStars 90dSame-day multiplierWeekly multiplierFortnight multiplierHot todayHot weekBreakoutStored score
Svelte

Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.40 Γ— Hot today + 0.40 Γ— Hot week + 0.20 Γ— Breakout.

  • Same-day multiplier = stars 1d Γ· max(1, stars 7d Γ· 7)
  • Weekly multiplier = stars 7d Γ· max(1, stars 30d Γ· 30 Γ— 7)
  • Fortnight multiplier = stars 14d Γ· max(1, stars 90d Γ· 90 Γ— 14)
  • Hot today = clamp(70 Γ— log-scale(stars 1d, 1000) + 30 Γ— breakout-scale(same-day, 4))
  • Hot week = clamp(75 Γ— log-scale(stars 7d, 5000) + 25 Γ— breakout-scale(weekly, 3))
  • Breakout = clamp(35 Γ— breakout-scale(same-day, 4) + 40 Γ— breakout-scale(weekly, 3) + 25 Γ— breakout-scale(fortnight, 2.5))
DateStarsStars 1dStars 7dStars 14dStars 30dStars 90dSame-day multiplierWeekly multiplierFortnight multiplierHot todayHot weekBreakoutStored score
Preact

Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.40 Γ— Hot today + 0.40 Γ— Hot week + 0.20 Γ— Breakout.

  • Same-day multiplier = stars 1d Γ· max(1, stars 7d Γ· 7)
  • Weekly multiplier = stars 7d Γ· max(1, stars 30d Γ· 30 Γ— 7)
  • Fortnight multiplier = stars 14d Γ· max(1, stars 90d Γ· 90 Γ— 14)
  • Hot today = clamp(70 Γ— log-scale(stars 1d, 1000) + 30 Γ— breakout-scale(same-day, 4))
  • Hot week = clamp(75 Γ— log-scale(stars 7d, 5000) + 25 Γ— breakout-scale(weekly, 3))
  • Breakout = clamp(35 Γ— breakout-scale(same-day, 4) + 40 Γ— breakout-scale(weekly, 3) + 25 Γ— breakout-scale(fortnight, 2.5))
DateStarsStars 1dStars 7dStars 14dStars 30dStars 90dSame-day multiplierWeekly multiplierFortnight multiplierHot todayHot weekBreakoutStored score
Solid

Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.40 Γ— Hot today + 0.40 Γ— Hot week + 0.20 Γ— Breakout.

  • Same-day multiplier = stars 1d Γ· max(1, stars 7d Γ· 7)
  • Weekly multiplier = stars 7d Γ· max(1, stars 30d Γ· 30 Γ— 7)
  • Fortnight multiplier = stars 14d Γ· max(1, stars 90d Γ· 90 Γ— 14)
  • Hot today = clamp(70 Γ— log-scale(stars 1d, 1000) + 30 Γ— breakout-scale(same-day, 4))
  • Hot week = clamp(75 Γ— log-scale(stars 7d, 5000) + 25 Γ— breakout-scale(weekly, 3))
  • Breakout = clamp(35 Γ— breakout-scale(same-day, 4) + 40 Γ— breakout-scale(weekly, 3) + 25 Γ— breakout-scale(fortnight, 2.5))
DateStarsStars 1dStars 7dStars 14dStars 30dStars 90dSame-day multiplierWeekly multiplierFortnight multiplierHot todayHot weekBreakoutStored score

Reliability score

Weekly average

100500
Full metrics details

Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.

Core

Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.30 Γ— Continuity + 0.30 Γ— Closure + 0.20 Γ— Shipping + 0.10 Γ— Liveness + 0.10 Γ— Support burden.

  • Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
  • Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
  • Shipping = 100 Γ— (20% Γ— release ratio 30d + 30% Γ— release ratio 90d + 50% Γ— release ratio 180d); ratios are releases Γ· 2, 6, and 12, capped at 1
  • Support burden = 100 βˆ’ 2 Γ— open issues per 1,000 stars
  • Liveness = 100 Γ— exp(βˆ’pushed days ago Γ· 120)

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.

DateIssues openedIssues closedPRs openedPRs mergedReleasesStarsOpen issuesPushed days agoContinuityClosureShippingLivenessSupport burdenLicenseObserved daysMissing daysNeeds healingStored score
React

Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.30 Γ— Continuity + 0.30 Γ— Closure + 0.20 Γ— Shipping + 0.10 Γ— Liveness + 0.10 Γ— Support burden.

  • Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
  • Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
  • Shipping = 100 Γ— (20% Γ— release ratio 30d + 30% Γ— release ratio 90d + 50% Γ— release ratio 180d); ratios are releases Γ· 2, 6, and 12, capped at 1
  • Support burden = 100 βˆ’ 2 Γ— open issues per 1,000 stars
  • Liveness = 100 Γ— exp(βˆ’pushed days ago Γ· 120)

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.

DateIssues openedIssues closedPRs openedPRs mergedReleasesStarsOpen issuesPushed days agoContinuityClosureShippingLivenessSupport burdenLicenseObserved daysMissing daysNeeds healingStored score
Angular

Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.30 Γ— Continuity + 0.30 Γ— Closure + 0.20 Γ— Shipping + 0.10 Γ— Liveness + 0.10 Γ— Support burden.

  • Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
  • Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
  • Shipping = 100 Γ— (20% Γ— release ratio 30d + 30% Γ— release ratio 90d + 50% Γ— release ratio 180d); ratios are releases Γ· 2, 6, and 12, capped at 1
  • Support burden = 100 βˆ’ 2 Γ— open issues per 1,000 stars
  • Liveness = 100 Γ— exp(βˆ’pushed days ago Γ· 120)

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.

DateIssues openedIssues closedPRs openedPRs mergedReleasesStarsOpen issuesPushed days agoContinuityClosureShippingLivenessSupport burdenLicenseObserved daysMissing daysNeeds healingStored score
Svelte

Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.30 Γ— Continuity + 0.30 Γ— Closure + 0.20 Γ— Shipping + 0.10 Γ— Liveness + 0.10 Γ— Support burden.

  • Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
  • Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
  • Shipping = 100 Γ— (20% Γ— release ratio 30d + 30% Γ— release ratio 90d + 50% Γ— release ratio 180d); ratios are releases Γ· 2, 6, and 12, capped at 1
  • Support burden = 100 βˆ’ 2 Γ— open issues per 1,000 stars
  • Liveness = 100 Γ— exp(βˆ’pushed days ago Γ· 120)

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.

DateIssues openedIssues closedPRs openedPRs mergedReleasesStarsOpen issuesPushed days agoContinuityClosureShippingLivenessSupport burdenLicenseObserved daysMissing daysNeeds healingStored score
Preact

Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.30 Γ— Continuity + 0.30 Γ— Closure + 0.20 Γ— Shipping + 0.10 Γ— Liveness + 0.10 Γ— Support burden.

  • Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
  • Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
  • Shipping = 100 Γ— (20% Γ— release ratio 30d + 30% Γ— release ratio 90d + 50% Γ— release ratio 180d); ratios are releases Γ· 2, 6, and 12, capped at 1
  • Support burden = 100 βˆ’ 2 Γ— open issues per 1,000 stars
  • Liveness = 100 Γ— exp(βˆ’pushed days ago Γ· 120)

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.

DateIssues openedIssues closedPRs openedPRs mergedReleasesStarsOpen issuesPushed days agoContinuityClosureShippingLivenessSupport burdenLicenseObserved daysMissing daysNeeds healingStored score
Solid

Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.

180 observed daily rows. Missing days are not fabricated.

Per-day formula: 0.30 Γ— Continuity + 0.30 Γ— Closure + 0.20 Γ— Shipping + 0.10 Γ— Liveness + 0.10 Γ— Support burden.

  • Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
  • Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
  • Shipping = 100 Γ— (20% Γ— release ratio 30d + 30% Γ— release ratio 90d + 50% Γ— release ratio 180d); ratios are releases Γ· 2, 6, and 12, capped at 1
  • Support burden = 100 βˆ’ 2 Γ— open issues per 1,000 stars
  • Liveness = 100 Γ— exp(βˆ’pushed days ago Γ· 120)

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.

DateIssues openedIssues closedPRs openedPRs mergedReleasesStarsOpen issuesPushed days agoContinuityClosureShippingLivenessSupport burdenLicenseObserved daysMissing daysNeeds healingStored score

If you evaluate alternatives, you will most often compare Vue against React, Angular, Svelte, Preact, and Solid.

Project Repo Adoption confidence (~6mo) PRs merged (~6mo) Star growth (~6mo)
Vue https://github.com/vuejs/core metrics pending 0 -30
React https://github.com/facebook/react metrics pending 0 1100
Angular https://github.com/angular/angular 69.95 1844 4372
Svelte https://github.com/sveltejs/svelte 75.59 984 5643
Preact https://github.com/preactjs/preact metrics pending 0 0
Solid https://github.com/solidjs/solid metrics pending 0 0

Best overall alternative: React. You get the broadest library surface, mature long-term ecosystem depth, and consistently strong maintenance signals across tools your team may already run.

Conclusion

Vue core is strongest when your team wants a clean path from small interactive views to large applications with reusable logic and predictable state updates. You trade some architectural freedom for the need to enforce conventions early, especially around component patterns and shared state.

Your most important engineering takeaway is to treat conventions as first-class architecture from day one while building on the official repository, documentation, and community discussions for implementation and maintenance decisions.

Join the conversation

Reviews Β· Questions Β· Posts

Share what you know about core β€” write a review from your real experience, ask an implementation question, or publish a post about how you use it.

Share your experience

Write or update your review

Explain what worked, what broke down, and what another team should know before adopting core.

Write your review now β€” it saves locally and publishes automatically after you sign in.

Rating
Positive attributes
Negative attributes

Project Q&A

Questions and answers

Browse implementation threads tied directly to vuejs/core. Each question links through to the full answer page.

Q&A No threads yet

Be the first to ask how teams run core in production. Every question you post becomes a durable, searchable answer page other developers can find.

Ask the first question

Related posts

Posts tagged with the same topics

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.

Posts No topic-linked posts yet

Share how your team uses core β€” a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.

Write the first post
Get a weekly email with the hottest new projects in the Vue Ecosystem and Vue Server Side Rendering & Static Generation world.
No Spam. Unsubscribe easily at any time.

Copyright 2018-2026 Awesome Open Source.  All rights reserved.