Open Source PowerShell Libraries

The SVG Explorer Extension is a utility for Windows File Explorer that adds native thumbnail rendering and context-menu previews for SVG files. With this extension installed, Explorer will show scalable previews of .svg files just like image formats, enabling visual quick identification of vector files. The project also adds a “Preview in Windows Explorer” feature so users can see full-size SVGs in the side preview pane without launching an editor. It supports features like CSS-based styling, embedded fonts, and scaling in thumbnails so the preview matches rendering expectations. Because Windows doesn’t natively render SVG previews in many versions, this fills a usability gap for designers, developers, and content creators working with vector assets. The extension is lightweight, integrates into shell UI seamlessly, and improves file navigation workflows involving vectors.

Vcpkg helps you manage C and C++ libraries on Windows, Linux and MacOS. This tool and ecosystem are constantly evolving, and we always appreciate contributions! After you've gotten vcpkg installed and working, you may wish to add tab completion to your shell. With CMake, you will still need to find_package and the like to use the libraries. Check out the CMake section for more information, including on using CMake with an IDE. In classic mode, vcpkg produces an "installed" tree, whose contents are changed by explicit calls to vcpkg install or vcpkg remove. The installed tree is intended for consumption by any number of projects: for example, installing a bunch of libraries and then using those libraries from Visual Studio, without additional configuration. Because the installed tree is not associated with an individual project, it's similar to tools like brew or apt, except that the installed tree is vcpkg-installation-local, rather than global to a system or user.

This repository contains the source code used to create the VM images for GitHub-hosted runners used for Actions, as well as for Microsoft-hosted agents used for Azure Pipelines. To build a VM machine from this repo's source, see the instructions.

Penetration-Testing-Tools is a curated collection of tools, scripts, cheatsheets and reference materials assembled to help security researchers, red-teamers, and students perform hands-on penetration testing across multiple domains. The repository groups resources by discipline — reconnaissance, web application testing, network exploitation, privilege escalation, post-exploitation and reporting — so users can quickly find relevant utilities and walkthroughs. Many entries include short usage notes, common command examples, and links to upstream projects or writeups, turning the repo into both a toolbox and a practical learning library. The collection emphasizes tooling that is easy to run in lab environments and often points to small scripts and one-file utilities that accelerate common tasks like service discovery, credential harvesting, or privilege checks.

This repository collects practical, real-world examples of using Ansible to automate infrastructure, deployments, and configurations. Each directory demonstrates a specific use case—ranging from setting up web servers, load balancers, and databases to orchestrating multi-tier applications in cloud environments. The examples highlight common Ansible practices such as organizing inventories, writing reusable playbooks, using roles, and handling variables and templates. They’re designed to be adapted directly into your own infrastructure or to serve as reference blueprints when learning how to structure automation projects. Whether you’re managing a handful of servers or deploying at scale, this repo provides starting points that illustrate how Ansible can streamline repetitive operational tasks.

- Suitable for mobile apps, enterprise software in C#, data science tasks. - Can be easily used as a local database in C# application or used as database server. - Nested data structures supported. - PowerShell interface for interactive mode and scripting. See project Wiki for more.

PowerShell-Suite is a curated collection of PowerShell utility scripts and modules created to provide low-level Windows API access, process manipulation, debugging detection, security operations, and post-exploitation techniques directly from PowerShell. The project is licensed under BSD-3-Clause. Among its components, there are scripts like Invoke-Runas (to launch processes under alternate credentials via CreateProcessWithLogonW), Invoke-CreateProcess (to spawn processes with fine control over flags, window state, etc.), Detect-Debug (to detect kernel or user mode debugging environments), Get-Handles (to enumerate handles in a process via NtQuerySystemInformation), Get-TokenPrivs (to inspect privileges on process tokens), Get-Exports (to parse DLL exports without loading DLLs), Masquerade-PEB (to alter the PEB of a process to appear as a different process), and UAC-TokenMagic (a method to bypass UAC via token manipulation).

PowerShellForGitHub is a PowerShell module that wraps the GitHub API, allowing administrators and developers to script common GitHub operations directly from the shell. It provides cmdlets for repository management, issue and pull request automation, organization and team administration, and policy tasks such as branch protection or collaborator invites. The module handles authentication flows, pagination, and rate-limit concerns transparently so scripts can focus on business logic like triage, bulk updates, or migration tasks. Because it returns structured objects, outputs are easy to pipe into other PowerShell commands for filtering, reporting, or storage. This makes it a natural fit for CI/CD orchestrations, scheduled housekeeping jobs, or bulk on-boarding workflows where manual web UI clicks would be tedious and error-prone. With commands that mirror everyday GitHub activities, the module helps integrate repository management into standard PowerShell automation estates.

A single fact determines the starting point of configuration, and that fact can be the same regardless of whether the software is running standalone under a logged-in user's account, or launched from another program with debugger access, or as a service or daemon, or even as a component within a dynamically linked library.