Basic PowerShell repo stats
5 days ago

PowerShell/PowerShell is an open source project licensed under MIT License which is an OSI approved license.

PowerShell Alternatives

Similar projects and alternatives to PowerShell

  • GitHub repo terminal

    The new Windows Terminal and the original Windows console host, all in the same place!

  • GitHub repo eShopOnContainers

    Cross-platform .NET sample microservices and container based application that runs on Linux Windows and macOS. Powered by .NET 5, Docker Containers and Azure Kubernetes Services. Supports Visual Studio, VS for Mac and CLI based environments with Docker CLI, dotnet CLI, VS Code or any other code editor.

  • GitHub repo dnSpy

  • GitHub repo ShareX

    ShareX is a free and open source program that lets you capture or record any area of your screen and share it with a single press of a key. It also allows uploading images, text or other types of files to many supported destinations you can choose from.

  • GitHub repo ASP.NET Core

    ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.

  • GitHub repo CodeHub

    CodeHub is an iOS application written using Xamarin

  • GitHub repo Wox

    Launcher for Windows, an alternative to Alfred and Launchy.

  • GitHub repo windows-rs

    Rust for Windows

  • GitHub repo PowerToys

    Windows system utilities to maximize productivity

  • GitHub repo shadowsocks-windows

    A C# port of shadowsocks

  • GitHub repo ShellCheck

    ShellCheck, a static analysis tool for shell scripts

  • GitHub repo v2rayN

  • GitHub repo WaveFunctionCollapse

    Bitmap & tilemap generation from a single example with the help of ideas from quantum mechanics

  • GitHub repo PSReadLine

    A bash inspired readline implementation for PowerShell

  • GitHub repo oil

    A new Unix shell. Our upgrade path from bash to a better language and runtime.

  • GitHub repo crux

    General purpose bitemporal database for SQL, Datalog & graph queries

  • GitHub repo jc

    CLI tool and python library that converts the output of popular command-line tools and file-types to JSON or Dictionaries. This allows piping of output to tools like jq and simplifying automation scripts.

  • GitHub repo Json.NET

    Json.NET is a popular high-performance JSON framework for .NET

  • GitHub repo Fable: F# |> BABEL

    F# to JavaScript Compiler

  • GitHub repo QMetaObject crate for Rust

    Integrate Qml and Rust by building the QMetaObject at compile time.

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better PowerShell alternative or higher similarity.


Posts where PowerShell has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-06-14.
  • Tutorial request: Parser
    If you want to look at how PowerShell does it, the source code for ConvertTo-Json is here and because it uses the Newtonsoft.Json library, that source code (which does the real work) ends up calling this Serialize() function
  • How to Build SQL Database Deployment Automation Pipeline [Tutorial] | 2021-06-10
  • What is PowerShell splatting and how does it work?
    I believe there's an rfc/pr for this on the powershell github here.
  • Copy command Confusion
    Also the related issue: The underlying FileSystemProvider as used within Copy-Item operation is likely the underlying cause of things not being "as expected". MS acknowledge this needs substantial rewrite and fixes but, to date, this has never been completed.
    Copy-Item can be very problematic and it has been since the beginning. Please refer here: Looking at that issue report I might suggest that wrapping a usage of Robocopy command will likely prove more reliable and consistent behaviour. You don't describe whether $dirSupportFiles is local or network shared location? I might also suggest you should look into the -Credentials option which I suspect could be tied to your issue - please note that your desired target location is primarily owned by the SYSTEM account, whilst local administrators can also have fuller access local users will default to read-only. There can be many underlying technical challenges with certain operations but a common failure cause can be "files in use" - open file handles in other process or even "self" that then can interfere/prevent action from completing: it likely requires more complex consideration than "Copy-Item" implements internally. You may not actually be doing anything "wrong", per se, but as per the issue report I highlight this command is not quite as consistent or straightforward as you may hope!!
  • The PowerShell IRC has moved to
  • OpenSUSE Leap 15.3 Released | 2021-06-02
    Yes, as a 10-year user of Tumbleweed, generally OpenSUSE is left behind when it comes to downloading binary packages from first-party sources.

    Even for the Microsoft software that "supports" OpenSUSE, historically that support was by expecting OpenSUSE users to use their RHEL packages which didn't always work well. [1] [2] (I don't know if the problems are still there, because I switched to the Docker image for `az` and stopped using `powershell`)



  • Capturing powershell 7 update message at start of console////
    PowerShell $r = Invoke-WebRequest -Method Head If (($r.BaseResponse.RequestMessage.RequestUri.Segments -match '^v7\.1.*') -notmatch $PSVersionTable.GitCommitId) {"Not Latest Release"}
  • New PowerShell Version - v7.2.0-preview.6: [7.2.0-preview.6] - 2021-05-27
  • SYSTEM unable to write to Public Desktop might be relevant
  • Windows Terminal Preview 1.9 Release
    Opened and
    pwsh.exe, or "PowerShell Core" though, is receiving updates. You might be able to ask on their repo,
  • Is there an efficient way to delete a list of 5,000 files from a directory containing 24,000?
  • AZ900 passed on second try