Repository brief

romkatv/powerlevel10k

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:56:48.031Z
3mo ago

romkatv/powerlevel10k

romkatv/powerlevel10k is a widely used Zsh theme focused on speed, flexibility, and guided setup. The upstream repo is active as of 2026-03-14, has 53,512 stars and 2,397 forks, but the README explicitly says support is very limited, no new features are planned, and most bugs will go unfixed. For fork interest, it is a mature, stable codebase with a clear user-facing niche rather than an actively evolving project.

GitHub
Loading tags...
Stars53,512
Forks2,397
Default branchmaster
Last pushed2026-03-14T06:07:30Z
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 if you want Powerlevel10k with targeted compatibility and bug fixes, especially around git backend behavior and tricky environments. Stay with upstream if you want the most established baseline and do not need those extra fixes.

Prefer upstream unless you specifically need this fork’s custom prompt/icon changes or want to hack on an older reimplementation. For normal adopters, the fork looks materially behind and likely less complete.

Prefer upstream unless you specifically need this fork’s repository identity. It adds no visible capabilities and is behind on upstream fixes, so the main reason to choose it is organizational, not functional.

Prefer upstream unless you specifically need this frozen snapshot; this fork offers no visible added capability and is materially behind on maintenance and fixes.

Prefer upstream unless you specifically need this exact snapshot. This fork does not add features and is already behind upstream, so it is mainly useful as a frozen copy rather than a better-maintained alternative.

Prefer upstream unless you specifically need this exact old snapshot. This fork adds no visible features and is materially behind on fixes, so it is best treated as archival rather than an improved alternative.

Prefer upstream unless you specifically need this older snapshot; the fork adds no visible capabilities and mainly inherits the risk of being out of date.

Prefer upstream unless you specifically need this exact older snapshot. For normal use, the fork offers no added capability and is materially behind on maintenance and fixes.

Prefer upstream unless you specifically need this older snapshot. This fork adds no visible capabilities, is far behind upstream, and appears effectively abandoned.

Prefer upstream unless you have a hard reason to pin this exact old snapshot. This fork offers no added capability and is materially behind on maintenance.