Discofork
Repository brief

pear-devs/pear-desktop

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-30T19:50:36.696Z
1mo ago

pear-devs/pear-desktop

Pear Desktop is an actively maintained Electron-based desktop app/extension for YouTube Music. It has a large user and fork base, ships cross-platform builds, supports custom plugins, and includes tests, translation workflows, and packaging/configuration for macOS, Linux, and Windows. For fork interest, it looks like a mature, actively developed codebase with customization and release tooling already in place.

GitHub
Loading tags...
Stars31,229
Forks1,782
Default branchmaster
Last pushed2026-03-30T17:41:59Z
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
Selected

Choose this fork only if you want its specific older fixes or legacy behavior. For most adopters, upstream is the safer choice because it is still actively maintained and this fork is materially stale and far behind.

Choose this fork if the bundled extras are the point; choose upstream if you want broader maintenance, faster updates, and less divergence.

Prefer this fork if you want bundled convenience features and a narrower, more opinionated experience. Prefer upstream if you want the full plugin ecosystem, fresher maintenance, and lower divergence risk.

Choose this fork if you want the added fullscreen, lyrics, and adblocker-focused behavior and are okay with trailing upstream by a substantial margin. Choose upstream if staying current with the latest fixes and releases matters more than the fork's extras.

Choose this fork if you want a customized dev base with specific behavioral patches and expect to maintain it yourself. Choose upstream if you want the latest fixes, lower maintenance risk, and a cleaner upgrade path.

Choose this fork if your priority is automated nightly/dev builds and release workflow experimentation. Choose upstream if you want the broadest feature set, freshest fixes, and lower regression risk.

Prefer this fork if you want a more permissive, privacy-leaning Pear Desktop with explicit ad-blocking and login changes. Prefer upstream if you want the latest fixes, test coverage, and lower-maintenance stability.

Choose this fork only if the bundled extras matter more than staying current. If you want the latest fixes, packaging, and maintenance, upstream is the safer choice.

Choose this fork only if you want its bundled extras and do not need to stay current with upstream fixes; otherwise, the upstream project is the safer default.

Choose this fork if your priority is adblocker restoration and a couple of targeted runtime fixes; avoid it if you want the most current upstream Pear Desktop experience, because it is substantially behind and appears to track only a small subset of the parent project's ongoing work.