Discofork
Repository brief

PowerShell/PowerShell

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-30T16:03:48.161Z
1mo ago

PowerShell/PowerShell

PowerShell/PowerShell is the main upstream repository for PowerShell 7+ and higher, with a large and active community: 52,181 stars, 8,237 forks, and recent commits through 2026-03-30. It is a cross-platform automation and configuration tool/framework for Windows, Linux, and macOS, with a shell, scripting language, and cmdlet-processing framework. Forks are likely interesting if you care about the current PowerShell 7.x codebase, packaging/build pipelines, tests, documentation, or platform support work; this repo is not the place for Windows PowerShell 5.1 issues.

GitHub
Loading tags...
Stars52,181
Forks8,237
Default branchmaster
Last pushed2026-03-30T07:37:19Z
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

9 of 9 fork briefs
Selected

Choose this fork only if you need PowerShell with security features deliberately stripped out. If you want a current, supported automation shell, upstream PowerShell is the better choice.

Prefer this fork if you need a customized PowerShell distribution or are willing to trade upstream freshness for downstream behavior and packaging changes. Prefer upstream if you want the most current, broadly validated PowerShell 7.x experience.

Prefer this fork only if you specifically want its older local packaging and workflow changes. For general PowerShell use, upstream is the safer choice because this fork is stale and materially behind current PowerShell 7.x.

Choose upstream unless you specifically need this fork's older snapshot; there is no evident downstream enhancement here, only upstream lag.

Choose this fork if you want PowerShell 7+ with targeted usability changes and are comfortable tracking upstream for the rest. Choose upstream instead if you want the latest release and the broadest maintained feature set.

Prefer this fork only if you need its custom behavior or packaging pipeline and are prepared to own merge debt. If you want a stable, current PowerShell 7 experience with minimal surprises, upstream is the safer choice.

Prefer this fork only if you specifically want TravisEz13's branch naming or a near-upstream personal workspace; otherwise upstream is the better adoption target because this fork adds no visible functionality and is already behind.

Choose this fork only if you need its custom packaging and behavior changes badly enough to accept major upstream drift and maintenance cost. For most adopters, upstream PowerShell is the safer choice.

Prefer this fork only if you specifically need its older 2019-era customizations. For most users, current upstream PowerShell is the better choice because this fork is stale, materially behind, and likely missing many modern fixes and release pipeline improvements.