/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

vuejs/awesome-vue

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T12:08:52.306Z

3mo ago

vuejs/awesome-vue

`vuejs/awesome-vue` is a large, active curated link collection for the Vue.js ecosystem. It is not archived, has very high adoption signals (73,616 stars and 9,486 forks), and was updated on 2026-03-30 after a push on 2026-03-27. The repo appears to be primarily a README-driven index with supporting assets and GitHub workflow content.

Loading tags...

Stars73,616

Forks9,486

Default branchmaster

Last pushed2026-03-27T08:14:33Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose upstream if you want the current Vue ecosystem directory. Choose this fork only if you specifically want an older, customized snapshot with added repo-info material and do not need ongoing freshness.

Prefer upstream unless you explicitly want a frozen snapshot. This fork adds no visible functionality and is 174 commits behind, so it is weaker for current Vue ecosystem discovery but acceptable as a static reference copy.

Prefer upstream unless you specifically want a frozen copy. This fork adds no visible capabilities and is materially behind, so it is weaker for anyone seeking current Vue ecosystem recommendations.

Choose this fork only if the added `mevn-boilerplate` entry is specifically useful to you. Otherwise, upstream is clearly the better default because it is far more current and actively maintained.

Choose this fork only if you want a historical, customized copy of `awesome-vue`. For anyone using the list to evaluate modern Vue resources, upstream is far better because this fork is stale and materially behind current curation.

Prefer upstream unless you specifically want an old, customized snapshot with repo-info content; this fork is too stale for users who need current Vue ecosystem coverage.

Choose the fork only if you want a frozen, repository-info-heavy snapshot. If you need current Vue resources, active curation, or upstream maintenance tooling, the upstream repository is the better choice.

Choose this fork only if you want a frozen, lightly customized copy of Awesome Vue. If you want current ecosystem coverage and active curation, upstream is the better choice.

Choose this fork only if you specifically want a stale, fork-owned Vue catalog with extra repo info; otherwise upstream is the better default because it is actively maintained and much more current.

Prefer upstream unless you specifically need this old snapshot or the repo-info-enhanced markdown artifact. For active Vue ecosystem discovery, this fork is too stale and has lost too much maintenance automation to be a better default.

Fork comparison

vuejs-tips/awesome-vue

38/100

stale

significant_divergence

Choose upstream if you want the current Vue ecosystem directory. Choose this fork only if you specifically want an older, customized snapshot with added repo-info material and do not need ongoing freshness.

Likely purpose

To maintain a personalized or annotated Vue resources index based on an older awesome-vue snapshot, likely with added repository information and local curation rather than tracking upstream closely.

Best for

People who want a historical snapshot of awesome-vue with extra repository context.; Teams building their own curated Vue resource index from an older baseline.; Users who prefer a simpler fork they can edit manually rather than follow upstream automation.

Additional features

A large `awesome_vue_with_repo_info.md` companion document that appears to add repository-level context and metadata.
A rewritten README that suggests a custom presentation or curated subset of the Vue resource catalog.
Local cleanup of contributing and workflow-related docs, implying a simpler fork workflow for maintainers.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

Upstream has continued active curation well past this fork, so it likely misses many newer Vue resources, tools, and examples added after 2017.
Removal of upstream PR template and workflow files makes contribution and automated README maintenance harder.
The fork is materially behind upstream, so it likely lacks the newer duplicate cleanup and Vue 2-only entry removals that keep the list current.
It appears to lag upstream's ongoing maintenance cadence, making it less suitable as a living reference index.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Useful if you want an older stable snapshot with custom repo context.
Could be easier to read if you prefer a more locally curated README over the full upstream catalog.
May fit teams maintaining a forked resource list with their own metadata or editorial process.

Risks

High drift from upstream means resource quality and coverage are likely outdated.
Users may assume it reflects current Vue ecosystem recommendations when it does not.
Maintenance automation appears reduced, so the list may rot faster than upstream.