This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| PowerShell Core | |
|---|---|
| Name | PowerShell Core |
| Developer | Microsoft |
| Latest release | 7.x |
| Programming language | C#, C++ |
| Operating system | Windows, macOS, Linux |
| Platform | .NET Core, .NET 5+ |
| License | MIT License |
PowerShell Core is a cross-platform command-line shell and scripting language originally developed by Microsoft and later maintained by a community-driven project under the aegis of the [.NET] ecosystem. It unifies interactive shell features, automation primitives, and object-based pipelines for system administrators, developers, and DevOps engineers across Windows Server, Ubuntu, Red Hat Enterprise Linux, macOS, Debian, Alpine Linux, CentOS and cloud platforms such as Microsoft Azure, Amazon Web Services, and Google Cloud Platform. The project evolved from a Windows-centric toolset into an open-source runtime aligned with modern .NET Foundation initiatives and cross-platform tooling strategies adopted by enterprises like GitHub, Docker, Kubernetes, HashiCorp, VMware, and Red Hat.
PowerShell Core traces origins to internal efforts at Microsoft to create a task automation framework influenced by work at Windows NT teams, management initiatives like System Center, and scripting practices found in tools such as WSH and shells on UNIX. Key milestones include public demonstrations at events such as TechEd, development influenced by engineers from CLR teams and the Windows PowerShell team, the open-sourcing announcement at Microsoft Build and subsequent hosting on GitHub. Community governance evolved through contributions from individuals affiliated with organizations like Red Hat, Canonical, Google, Amazon, VMware, Chef Software, Puppet Labs, and standards groups within the .NET Foundation.
PowerShell Core introduces a rich set of features including a pipeline that transports .NET objects, cmdlets authored in C#, interactive Read-Eval-Print Loop (REPL) experiences similar to shells used by Linux Foundation distributions, and integrated help systems reminiscent of documentation approaches at Mozilla Foundation and Apache Software Foundation projects. It supports scripting constructs and modules compatible with community projects from GitHub, offers tab completion influenced by shells like Bash and Zsh, and integrates with editors and IDEs such as Visual Studio Code, Visual Studio, JetBrains Rider, Sublime Text, and Atom. Extension points allow integration with configuration management tools created by Chef Software, Puppet Labs, Ansible, and orchestration platforms like Kubernetes and Docker.
The runtime architecture leverages .NET Core and later .NET 5 and .NET 6 releases to provide a managed execution environment, interoperating with native APIs on Windows Server, macOS Big Sur, Ubuntu LTS, and containerized images run on Docker Engine and Kubernetes. The host process model enables embedding in services produced by vendors such as Microsoft Azure, Amazon Web Services, and Google Cloud Platform, while platform abstraction layers borrow patterns from projects like Mono and interoperability efforts seen in Wine and Cygwin. Packaging and distribution follow practices used by Debian Project, Ubuntu, Red Hat, SUSE, and Homebrew.
Compatibility strategies for modules rely on a combination of binary compatibility, module manifest metadata, and remoting adapters; community contributors from GitHub and enterprise teams at Microsoft and Red Hat maintain shims and compatibility layers. The PowerShell Gallery ecosystem interacts with package repositories and tooling used by NuGet, Chocolatey, APT, YUM, Homebrew, and Scoop. Integration adapters and modules are commonly authored by teams at Microsoft Exchange, Active Directory engineering groups, cloud services teams at Amazon Web Services, Google Cloud Platform, and third-party vendors like VMware, Cisco Systems, Palo Alto Networks, F5 Networks, and Fortinet.
Security model components include code signing practices aligned with standards used by Federal Information Processing Standards, policy enforcement similar to approaches at OpenSSH projects, and authentication flows that interoperate with identity providers such as Active Directory, Azure Active Directory, Okta, Ping Identity, and LDAP directories used by enterprises like IBM and Oracle. Remoting capabilities leverage protocols and transports informed by SSH implementations, WinRM concepts, and secure channel patterns used in TLS stacks maintained by organizations such as IETF and OpenSSL contributors. Community and vendor security audits involve teams from Microsoft Security Response Center, open-source auditors like OWASP, and independent researchers affiliated with academic institutions such as MIT, Stanford University, and Carnegie Mellon University.
Performance tuning for PowerShell Core is evaluated against workloads typical of infrastructure automation and data processing, with benchmarks produced by organizations and projects including SPEC, Phoronix Test Suite, and community repositories on GitHub. Runtime optimizations track progress in .NET Runtime improvements contributed by teams at Microsoft and the broader dotnet community, while profiling and diagnostic tooling integrate with products from JetBrains, Redgate, New Relic, Datadog, Dynatrace, and the Windows Performance Toolkit. Comparative studies frequently reference scripting environments like Bash, Python, and Ruby in performance analyses by academic and industry groups such as ACM and IEEE conferences.
Adoption spans system administration, cloud automation, CI/CD pipelines, and configuration management across organizations including Microsoft Azure, Amazon Web Services, Google Cloud Platform, GitHub, GitLab, Atlassian, Red Hat, IBM, Oracle, and financial institutions regulated by PCI DSS frameworks. Common use cases include automated provisioning with tools from HashiCorp and Terraform, orchestration within Kubernetes clusters, Continuous Integration workflows in Jenkins and Azure DevOps, incident response practices influenced by teams at Mandiant and CrowdStrike, and SRE processes adopted by companies like Netflix, Facebook, Twitter, LinkedIn, and Spotify.
Category:Command-line shells