Skip to content
PowerShellGet is the Package Manager for PowerShell
Branch: development
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update issue template Oct 7, 2018
.vscode WIP: localdev publishing (#462) May 2, 2019
DSC Fix DscResources foldername (#521) Aug 10, 2019
Tests Fix test-path failure when retrieving credential provider (#526) Aug 16, 2019
Utilities/OfflinePowerShellGet Update OfflinePowerShellGetDeploy.psd1 Nov 5, 2018
imgs WIP: localdev publishing (#462) May 2, 2019
src/PowerShellGet Update module version to 2.2.2 (#557) Dec 11, 2019
tools WIP: localdev publishing (#462) May 2, 2019
v3prototype V3prototype (#525) Aug 15, 2019
.MetaTestOptIn.json Merge development into master (#431) Feb 26, 2019
.gitignore Merge development into master (#431) Feb 26, 2019
.travis.yml Merge development into master (#431) Feb 26, 2019 Merge development into master (#431) Feb 26, 2019
LICENSE Initial commit Sep 29, 2016 WIP: localdev publishing (#462) May 2, 2019
SignCat.xml Add config files for Azure DevOps code signing (#432) Mar 13, 2019
SignConfig.xml update casing of output (#529) Aug 22, 2019
appveyor.yml Merge development into master (#431) Feb 26, 2019

Join the chat at License Documentation - PowerShellGet PowerShell Gallery - PowerShellGet Minimum Supported PowerShell Version


PowerShellGet is a PowerShell module with commands for discovering, installing, updating and publishing the PowerShell artifacts like Modules, DSC Resources, Role Capabilities and Scripts.

PowerShellGet module is also integrated with the PackageManagement module as a provider, users can also use the PackageManagement cmdlets for discovering, installing and updating the PowerShell artifacts like Modules and Scripts.

Build status

Development branch

OS - PS Version Build Status
AppVeyor (Windows - PS 4.0) d-av-image
AppVeyor (Windows - PS 5.1) d-av-image
AppVeyor (Windows - PS 6.0.0+) d-av-image
Travis CI (Linux - PS 6.0.0+) d-tv-image
Travis CI (MacOS - PS 6.0.0+) d-tv-image

Master branch

OS - PS Version Build Status
AppVeyor (Windows - PS 4.0) m-av-image
AppVeyor (Windows - PS 5.1) m-av-image
AppVeyor (Windows - PS 6.0.0+) m-av-image
Travis CI (Linux - PS 6.0.0+) m-tv-image
Travis CI (MacOS - PS 6.0.0+) m-tv-image

Daily Build status

Development branch

OS - PS Version Build Status
AppVeyor (Windows - PS 4.0) d-n-av-image
AppVeyor (Windows - PS 5.1) d-n-av-image
AppVeyor (Windows - PS 6.0.0+) d-n-av-image
Travis CI (Linux - PS 6.0.0+) d-tv-image
Travis CI (MacOS - PS 6.0.0+) d-tv-image


Click here


  • Windows PowerShell 3.0 or newer.
  • PowerShell Core.

Module Dependencies

  • PackageManagement module

Get PowerShellGet Module

Please refer to our documentation for the up-to-date version on how to get the PowerShellGet Module.

Get PowerShellGet Source


cd path/to/PowerShellGet
  • Import the module
Import-Module src/PowerShellGet

Local Development

Visual Studio Code:-

  1. Open VSCode choosing "Run as Administrator"
  2. Select Terminal>Run Task>Install Dependencies
  3. Select Terminal>Run Task>Build and Import Module

for subsequent changes you can just run 'Build and Import Module' or press ctrl + shift + B

Standard PowerShell:-

  1. Open an administrative PowerShell prompt
  2. Run the following commands
Import-Module "$ClonePath\tools\build.psm1"

This will take the published module from ./dist and install it into the powershell module path under the current version of PowerShellGet apending 9999 to the version number.

An explicit or implicit (such as when the test suite is invoked) import of the PowerShell get module will ensure the module version under development gets loaded.

It is therefore easy to see with Get Module that the version under development is loaded, like this:-

alt text

To remove this module and revert to the production PowerShellGallery published version, simply remove the folder from the module path. (if running VSCode select Terminal>Run Task>Remove Development Module).

Running Tests


You can run the test task Terminal>Run Task>Run Full Test Suite

Non VSCode

Pester-based PowerShellGet Tests are located in <branch>/PowerShellGet/Tests folder.

Run following commands in PowerShell Console with Administrator privileges.

Import-Module "$ClonePath\tools\build.psm1"

Contributing to PowerShellGet

You are welcome to contribute to this project. There are many ways to contribute:

  • Submit a bug report via Issues. For a guide to submitting good bug reports, please read Painless Bug Tracking.
  • Read the documentation on contributing to open source and forking.
  • Verify fixes for bugs.
  • Submit your fixes for a bug. Before submitting, please make sure you have:
    • Performed code reviews of your own
    • Updated the test cases if needed
    • Run the test cases to ensure no feature breaks or test breaks
    • Added the test cases for new code
  • Submit a feature request.
  • Help answer questions in the discussions list.
  • Submit test cases.
  • Tell others about the project.
  • Tell the developers how much you appreciate the product!

You might also read these two blog posts about contributing code: Open Source Contribution Etiquette by Miguel de Icaza, and Don’t “Push” Your Pull Requests by Ilya Grigorik.

Before submitting a feature or substantial code contribution, please discuss it with the Windows PowerShell team via Issues, and ensure it follows the product roadmap. Note that all code submissions will be rigorously reviewed by the Windows PowerShell Team. Only those that meet a high bar for both quality and roadmap fit will be merged into the source.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.

You can’t perform that action at this time.