/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

slidevjs/slidev

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-30T11:57:49.563Z

3mo ago

slidevjs/slidev

slidevjs/slidev is a large, actively maintained open source presentation framework for developers. It is centered on Markdown-based slide authoring with themes, interactive Vue components, presenter mode, drawing, LaTeX, Mermaid diagrams, icons, built-in editor support, recording, and export to PDF/PNG/PPTX.

Loading tags...

Stars45,299

Forks1,988

Default branchmain

Last pushed2026-03-29T14:34:14Z

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

Prefer this fork only if you need its specific workflow changes and are prepared to own the maintenance burden. If you want the full, current Slidev feature set and active upstream fixes, upstream is the safer choice.

Prefer this fork only if you specifically want its VS Code and workflow customizations and are willing to maintain a significant divergence from upstream. If you want the newest Slidev features, fixes, and docs with lower operational risk, upstream is the safer default.

Prefer this fork only if its local presenter/export/editor changes match your needs and you are willing to own a stale, highly divergent codebase. If you want current Slidev features, compatibility, and lower maintenance risk, upstream is the better default.

Prefer upstream unless you specifically need this fork's older custom behavior. The fork is materially behind and stale, so it is a poor default choice for new adoption but may still fit legacy/internal deployments that need its local workflow changes.

Choose upstream unless you specifically need this fork’s older customized behavior. This fork is materially behind, stale, and likely missing several current Slidev capabilities; it only makes sense if you want a frozen beta baseline or a fork you plan to own end-to-end.

Prefer upstream unless you specifically need this fork’s custom behavior. Choose the fork only if its local changes are the product, because it is materially behind and structurally divergent from current Slidev.

Choose upstream unless you specifically need this exact fork as a starting point. It adds no clear new capabilities, and it is substantially behind on upstream maintenance.

Prefer upstream unless you need this exact fork snapshot; it adds no evident capabilities and is materially behind current Slidev.

Prefer upstream unless you specifically need this exact older snapshot; this fork adds no visible product value and mainly carries the cost of being behind.

Prefer this fork only if you need its specific internal customizations. For general Slidev use, upstream is the better choice because this fork is stale, substantially diverged, and appears to have removed or lagged on user-facing workflows like export and documentation.

Fork comparison

tanzinabd23/slidev

38/100

stale

significant_divergence

Prefer this fork only if you need its specific workflow changes and are prepared to own the maintenance burden. If you want the full, current Slidev feature set and active upstream fixes, upstream is the safer choice.

Likely purpose

To maintain a localized or experimental Slidev variant with updated tooling and documentation for a specific workflow, especially around VS Code integration, presenter usage, and internal authoring guidance.

Best for

Teams that want a customized Slidev workflow and are willing to maintain their own fork.; Users who care more about editor/presenter-specific tweaks than staying current with upstream.; Adopters who need a stabilized snapshot of Slidev features rather than the latest upstream release cadence.

Additional features

Expanded or rewritten Slidev skills and reference docs for authoring workflows and core concepts.
Changed presenter page behavior and layout, suggesting customization of the presentation control experience.
Updated VS Code integration files and slides tree/project handling, indicating a stronger editor-centric workflow.
Dependency and workspace reshaping via large pnpm-lock and workspace changes, which may reflect a customized build/setup pipeline.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

The fork is far behind upstream, with 200 commits behind and a last push in February 2025 while upstream remained active through March 2026.
Large deletions in core reference docs and generated client assets suggest some upstream documentation/support material or packaged behavior was removed or is no longer aligned.
Users relying on the latest upstream fixes and docs, including presenter-mode and CLI updates from 2026, will not have them here.
The fork may make some upstream editor/help content harder to use because several skill/reference files were substantially trimmed or rewritten.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Potentially better fit for a specific internal workflow or teaching setup.
More tailored VS Code and presenter-mode experience than stock upstream.
May reduce noise by pruning or replacing upstream docs and reference material with fork-specific guidance.

Risks

Material divergence from upstream makes merges and future upgrades expensive.
Being stale relative to upstream increases the chance of missing bug fixes and compatibility updates.
Removed or rewritten docs may make it harder for new adopters to understand standard Slidev behavior.
The fork’s intent is not obvious from metadata alone, so adoption risk is high unless you specifically need its custom workflow.