Welcome to the PowerShell GitHub Community! PowerShell is a cross-platform (Windows, Linux and OS X) 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.
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.
Platform | Downloads | How to Install |
---|---|---|
Windows 10 / Server 2016 | .msi | Instructions |
Windows 8.1 / Server 2012 R2 | .msi | Instructions |
Ubuntu 16.04 | .deb | Instructions |
Ubuntu 14.04 | .deb | Instructions |
CentOS 7 | .rpm | Instructions |
OS X 10.11 | .pkg | Instructions |
To install a specific version, visit releases.
Want to chat with other members of the PowerShell community?
Linux | Windows | OS X |
---|---|---|
Instructions | Instructions | Instructions |
If you have any problems building, please consult the developer FAQ.
AppVeyor (Windows) | Travis CI (Linux / OS X) |
---|---|
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.git
If you already cloned but forgot to use --recursive
, you can update submodules manually:
git submodule update --init
See 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.
PowerShell is licensed under the MIT license.
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 [email protected] with any additional questions or comments.