r/PowerShell • u/positivemark • 10d ago
Information Wanted: Awesome PowerShell Modules
Hey r/powershell! I've just published an Awesome PowerShell Modules list (using the awesome-lists format) in GitHub:
- https://github.com/markwragg/awesome-powershell-modules#readme
I used AI to assist with the curation, but it was built from a combination of my personal experience with many of the modules, as well as a scan of modules mentioned on the PowerShell Podcast, PowerShell Weekly newsletter, Powershell.news and some previous PowerShell related Awesome lists that I found.
I've tried to review as many of the modules as I could, but if anyone finds that there's a module listed that is no longer working please let me know. As a general rule, the list attempts to only include modules that are still actively being developed, or are feature complete. Modules where the GitHub repo has been archived (or appear largely abandoned), are intentionally excluded.
If you know of (or are the maintainer of) a module that you'd like included, please feel free to either let me know here or raise a PR. Ideally the module should make someone want to say "wow that's awesome" :), must be published in the PowerShell Gallery and be at least 30 days old.
There's a couple of PowerShell scripts under /scripts in the repo which you can use against the list. One returns all of the modules, their URLs, author and number of downloads. The other aggregates by author. The latter reveals that I put my own modules on the list 8 times, but hey It's my list and I'll use it to shamelessly self promote if I want to 😂.
7
u/Jagula 10d ago
Really good list so far. I was going to list out Evo's stuff (PSWriteHTML is probably my favorite module ever) but it looks like it's been accounted for.
A few I use that aren't on there yet:
Microsoft.WinGet.Client: official winget module. Nicer than parsing winget.exe output.
PowerSTIG: if you're in DoD or anywhere else STIGs ruin your life, it's pretty solid. DSC based and Microsoft maintains it.
NTFSSecurity: still the least painful way to deal with ACLs. I haven't found anything better, and it looks like it's being maintained again!
Shameless plug for my own project: PsUi, a framework meant to make WPF in PowerShell a bit less miserable.
Glad someone's keeping a list like this maintained, I starred it.
1
u/positivemark 7d ago
Added thanks! I traded NTFSSecurity for WindowsAccessControl, per the other comment.
If you want to highlight that you've been featured in the list, you can add this badge to your readme:
[](https://github.com/markwragg/awesome-powershell-modules#readme)But there's no pressure/requirement to do this at all.
1
u/Thotaz 10d ago
and it looks like it's being maintained again!
Actually, if you look at the readme it says:
NTFSSecurity will be archived soon. Please move to WindowsAccessControl, which is also on the PowerShell Gallery: Install-Module -Name WindowsAccessControl.
Looking at the new module, it seems great because now it can be used to manage the ACLs for other things as well.
5
u/Thotaz 10d ago
Cool list. I did a quick scan through the list, and I spotted 2 "mistakes".
1: VMware.PowerCLI has been deprecated and replaced by the newer VCF.PowerCLI module
2: AudioDeviceCmdlets has an open issue calling out that the project is unmaintained: https://github.com/frgnca/AudioDeviceCmdlets/issues/87 considering that there's been no response from the maintainer I can only assume that's true.
1
u/positivemark 10d ago
Both fixed thanks. Turns out there is a fork of the AudioDeviceCmdlets one that is being maintained, but isn't published in the PSGallery, so to avoid confusion and stay true to the list I just dropped it entirely.
1
u/dathar 10d ago
Dang on that AudioDeviceCmdlets. Was a wonderful little tool back when I had to manage a ton of demo computers and getting their audio devices and whatever people plugged in.
3
u/Thotaz 10d ago
To be fair, just because it's unmaintained does not mean it's bad. If you used it with great success back in the day, then you can still do those same things today.
Besides, in the listed issue there's 2 alternatives:1: A fork of the original module.
2: A completely separate module (AudioConfig)1
u/dathar 10d ago
It is more of a nostalgia thing as I haven't had to work on Windows systems in over 5 years now. We'd get demo stations where someone unplugs a usb headset and Windows decides to not set it as a default when they plug it back in. Good memories.
I still use unmaintained and abandonware. There's an old PowerShell script for Blink cameras that logs on and snags all the videos. Hasn't been updated in forever but that thing is a champ.
2
u/Thotaz 10d ago
God, that default audio thing reminds me of Teams. When I dock/undock my laptop Windows itself handles the audio switching just fine, but because Teams refuses to use the default Windows audio settings (despite being a Microsoft product) I still have to occasionally switch my audio and microphone sources to my headset.
There's been a ton of feedback threads about this, but because of their dominant market position they don't give a fuck about making an actually good product. If users had a choice, they wouldn't pick Teams, it's just what most IT departments use to make life easy (and cheap) for the admins.1
u/BlackV 10d ago
VMware.PowerCLI has been deprecated and replaced by the newer VCF.PowerCLI module
Oh really, for so many years the vmware powershell modules were the gold standard for high quality modules, there were doing better than MS in some cases
Its been so long since I touched it
1
u/Thotaz 10d ago
Don't worry, it's just a branding change for the root module. The underlying types and sub modules still use their old "vmware" naming convention, so nothing has actually changed besides the command used to install/import the whole PowerCLI suite.
And yes, PowerCLI was/is basically the golden standard for PowerShell modules with good use of all the PowerShell features (argument transformers, pipeline input) and sensible naming convention. It's too bad the broadcom purchase means that most IT users won't get to experience it in the future because it also served as great inspiration on how to design and use PowerShell modules/features.
5
u/MadBoyEvo 10d ago
Not sure if you have seen:
https://codeberg.org/janikvonrotz/awesome-powershell which used to be here: https://github.com/janikvonrotz/awesome-powershell
https://github.com/luke-beep/awesome-powershell - couple of others..
1
u/positivemark 10d ago
Yeah thanks, those are the ones I did source some input from. They are general PowerShell lists though (so cover blogs and other tools), where as mine is just modules to make it more specified and therefore able to hold more of that category specifically.
2
u/zero0n3 10d ago
Can you try and prioritize some forges?
I’m always interested in how people build scaffolding to facilitate their module building.
Ie setting up pipelines and tests and builds.
It’s so varied and would love to see some options to borrow from.
Unfortunately can’t release mine currently until I clean room design on my own time.
1
u/positivemark 10d ago
There's a few modules on the list under build and automation that touch on some of this, but I don't know if any of them go as far as to fully prescribe pipelines as there's a bit of personal preference there I think, and people use different CI/CDs. My build pipeline uses PSake, PSDeploy and BuildHelpers, which I think is quite typical.
I haven't used it but PowerShellBuild on the list was interesting to me as I think it offers standardised versions of a lot of the build tasks I already use.
I was building and deploying via Azure DevOps up until literally this week, and did a talk about it as PSConf.eu Minicon which you can watch here if its of interest: https://www.youtube.com/watch?v=x5LXjIPEflU&list=PLR-Vt0R0YIzw&index=4&t=2s
While prepping for that talk I discovered that Microsoft are stopping free accounts from being able to run parallel build jobs, which was going to be annoying for me as most of my modules I want to simultaneously test on Windows, MacOS and Linux for speed, so I have just migrated all my PS module repos to use GitHub Actions instead. I need to do a blog about that, but it wasn't too difficult a move (a lot of similarities) and actually I think the builds run faster.
2
u/BlackV 10d ago edited 10d ago
Microsoft.PowerShell.Crescendo and Microsoft.PowerShell.SecretManagement have all been sunset have they not? (I.e. should they stay on the lists)
1
u/positivemark 10d ago
I think you probably meant that to say Microsoft.PowerShell.Crescendo and Microsoft.PowerShell.SecretManagement. You're right, the escape my archived repo catch because the repo themselves isn't archived but their readme notes does say they should be considered as such so I should probably drop them from the list.
2
u/lurkelton 9d ago
Nice list, ImportExcel I use daily. 😊 I think PSAuthClient deserves a spot. (disclaimer: I'm the author) It's a OAuth2/OIDC that supports a wide range of grants (auth code + PKCE, device code, client credentials, JWT bearer etc), uses embedded WebView2 for interactive sign-in (SSO, Windows Hello, FIDO2 all work) plus helpers for decoding JWTs and validating signatures.
1
u/positivemark 7d ago
This looks great, I've added it to the list under Secrets & Security.
If you want to highlight that you've been featured in the list, you can add this badge to your readme:
[](https://github.com/markwragg/awesome-powershell-modules#readme)But there's no pressure/requirement to do this at all.
2
1
13
u/MadBoyEvo 10d ago
I'll leave it here:
https://www.powershellgallery.com/profiles/Przemyslaw.Klys
https://github.com/EvotecIT/
I'll let you be the judge. Some of the modules you listed undersell their value but I'll let it go 🤣