This repository contains reports for the PowerShell Gallery. The hope is that it will be easier for you to find modules that will make your work easier. The plan is to update the reports three times a day and push them to this repository.

Feel free to use the Discussion section of this repository to talk about specific modules. If you think there should be another type of report, feel https://github.com/jdhitsolutions/PSGalleryReport/issues free to submit a Feature Request in the Issues section of this repository.

⚠️ This project is not a PowerShell module for you to install and run. This repository is a location for reports that I am generating and publishing through a GitHub Action. You are welcome to take my scripts and use them as the basis for your own reporting. Or feel free to fork and keep up to date on your own.

These are the currently active reports. Reports are created in markdown. I have removed the PDF reports from the repository.

GitHub will render reports in your browser.

You are welcome to clone the repository or download individual reports. In PowerShell 7, you can use Show-Markdown to view markdown reports.

Show-Markdown .\psgallery-downloads.md -UseBrowser

The reports show the same information for each module. The only limiting factor is the report's scope.

This report will show the most recent 250 modules published to the PowerShell Gallery. The report is sorted by the published date in descending order. The report includes links to the project in the Gallery as well as the project's repository if defined. This list does not include any pre-release modules.

This report is identical to the previous report except that the AWS and Azure modules published by Amazon and Microsoft are excluded. There are many of these modules and they could easily consume most of the newest released module report.

This report gets the last 250 Azure-related modules published to the PowerShell Gallery. These are modules written by Microsoft and the community. The report is sorted by the published date in descending order.

This report is sorted by total download count and is limited to the first 250 PowerShell modules.

This report is sorted by total download count and limited to the first 250 modules where the author is not Microsoft, Oracle, VMware, Amazon, HP, or Dell. Contributions from the DSC Community are also excluded. Hopefully, this report highlights modules created by individual members of the PowerShell community.

This is a report of the top 25 module contributors to the PowerShell Gallery. The list excludes major vendors such as Microsoft and VMware. The exclusion criteria are admittedly arbitrary and subjective. The goal is to highlight individual contributions to the PowerShell Gallery.

The end of the list is essentially by chance. If there are 3 contributors with the same number of contributions at the end of the list, the contributor included in the list is essentially random. I am not intentionally slighting anyone.

This is a simple text list of unique tags found in the PowerShell Gallery. All tags have been converted to lowercase, but that should not affect the use of the tag.

Find-Module -tag bios

✋ Do not assume this is an authoritative or definitive list. Best efforts have been made to parse tags but tag definitions are not consistent across all published modules.

This repository will also contain a JSON file of export PSGallery information. You can import this file and use it to create your reports.

$data = Get-Content psgallerydata.json | ConvertFrom-JSON
$data | where-object {$_.name -match "(SQL)|(database)"} | Select-Object -property name,author,version,description,projecturi

I am using a Github action to generate the reports every 8 hours. The action is executing the run.ps1 script in the latest Ubuntu release.

As of now, there is no way to include pre-release modules. You can only use Find-Module to search for pre-release when using the module name. You can always click the PowerShell Gallery link in a report and check for pre-release versions.

I considered revising the scripts to use the newer and improved Microsoft.PowerShell.PSResourceGet module. However, I discovered that the module does not return the same information as PowerShellGet. Most importantly for my purposes, Find-PSResource does not include the download count. That defeats one of the primary purposes of this project.