Welcome to the PowerShell GitHub Community! PowerShell Core is a cross-platform (Windows, Linux, and macOS) automation and configuration tool/framework that works well with your existing tools and is optimized for dealing with structured data (e.g. JSON, CSV, XML, etc.), REST APIs, and object models. It includes a command-line shell, an associated scripting language and a framework for processing cmdlets.
Although this repo started as a fork of the Windows PowerShell code base, changes made in this repo do not make their way back to Windows PowerShell 5.1 automatically. This also means that issues tracked here are only for PowerShell Core 6.0. Windows PowerShell specific issues should be opened on UserVoice.
If you are new to PowerShell and would like to learn more, we recommend reviewing the getting started documentation.
You can download and install a PowerShell package for any of the following platforms.
You can download and install a PowerShell package for any of the following platforms, which are supported by the community.
| Platform | Downloads | How to Install |
|---|---|---|
| Arch Linux | Instructions | |
| Kali Linux | .deb | Instructions |
| Many Linux distributions | .AppImage | Instructions |
You can also download the PowerShell binary archives for Windows, macOS and Linux.
| Platform | Downloads | How to Install |
|---|---|---|
| Windows | 32-bit/64-bit | Instructions |
| macOS | 64-bit | Instructions |
| Linux | 64-bit | Instructions |
| Windows (arm) Experimental | 32-bit/64-bit | Instructions |
| Raspbian (Stretch) Experimental | .tgz | Instructions |
To install a specific version, visit releases.
Dashboard with visualizations for community contributions and project status using PowerShell, Azure, and PowerBI.
For more information on how and why we built this dashboard, check out this blog post.
Want to chat with other members of the PowerShell community?
We have a Gitter Room which you can join below.
There is also the community driven PowerShell Slack Team which you can sign up for at Slack Sign up.
Awesome PowerShell is a great curated list of add-ons and resources.
| Linux | Windows | macOS |
|---|---|---|
| Instructions | Instructions | Instructions |
If you have any problems building, please consult the developer FAQ.
| AppVeyor (Windows) | Travis CI (Linux / macOS) |
|---|---|
 |
| AppVeyor (Windows) | Travis CI (Linux) | Travis CI (macOS) | Code Coverage Status |
|---|---|---|---|
 |
 |
 |
The PowerShell repository has a number of other repositories embedded as submodules.
To make things easy, you can just clone recursively:
git clone --recursive https://github.com/PowerShell/PowerShell.gitIf you already cloned but forgot to use --recursive, you can update submodules manually:
git submodule update --initSee working with the PowerShell repository for more information.
Please see the Contribution Guide for how to develop and contribute.
If you have any problems, please consult the known issues, developer FAQ, and GitHub issues. If you do not see your problem captured, please file a new issue and follow the provided template. If you are developing .NET Core C# applications targeting PowerShell Core, please check out our FAQ to learn more about the PowerShell SDK NuGet package.
Also make sure to check out our PowerShell-RFC repository for request-for-comments (RFC) documents to submit and give comments on proposed and future designs.
PowerShell is licensed under the MIT license.
License: By requesting and using the Container OS Image for Windows containers, you acknowledge, understand, and consent to the Supplemental License Terms available on Docker hub:
By default, PowerShell collects the OS description and the version of PowerShell (equivalent to $PSVersionTable.OS and $PSVersionTable.GitCommitId) using Application Insights.
To opt-out of sending telemetry, delete the file DELETE_ME_TO_DISABLE_CONSOLEHOST_TELEMETRY before starting PowerShell from the installed location.
The telemetry we collect fall under the Microsoft Privacy Statement.
Governance policy for PowerShell project is described here.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.