There are 4 repositories under named-pipes topic.
A tool to capture communication between Chromium processes on Windows
.NET Core Inter-process communication framework
Asynchronous HTTP Botnet for Distributed Denial of Service (DDoS)
💻 Learn Bash streams, pipelines and redirection, from beginner to advanced.
A modern header-only C++ library that provides platform-independent utilities.
Named pipe transport for gRPC in C#/.NET
Intercept Windows Named Pipes communication using Burp or similar HTTP proxy tools
A .NET utility library to spawn, supervise and (optionally) cleanly shut down child processes.
Embedded web browser for Unity games, based on Chromium Embedded Framework (CEF)
A native named pipe wrapper for Unity3D
.NET library for using HTTP 1.1 over streams, especially Windows Named Pipes
Implementing IPC in Windows using Named Pipes with AIO
Proof of concept SMB C2 using named pipes in Golang
An MVC multi-process-architectured Revit add-in where the 'View' layer is implemented as an Electron.js app that communicates with the Revit add-in with a 'Controller' layer wrapped over a server/client architecture using named pipes.
A script in Python 3 to turn mpv into a DLNA / UPnP renderer
Steam emulator prototype using the Steam Pipe protocol.
A set of classes and modules for .Net development
A simple C# named pipe server implementation that can be used to share data with Node.js instances
VoltRpc - An RPC library which is designed to be both simple to use and fast.
A wrapper library and integration IPC server of the CeVIO API for .NET 7 / .NET Standard 2.0
Russel Libby's named pipes for Delphi as found on Francois Piette's blog on http://francois-piette.blogspot.com/2013/04/inter-process-communication-using-pipes.html
SignalR Core Named Pipe Transport
protobuf-pbop-plugin is a C++ open-source plugin for Google Protocol Buffers which provides inter-process communication (IPC) over Windows Named Pipes. The acronym PBOP is for Protocol Buffers Over Pipe (PBOP)
This is a sample application demonstrating how to use named pipes to establish a communication between a Revit plugin and a console application. The console application is an IFC files loader that is built on top of xBIM toolkit. Although this is a great demo how to use Named Pipe to establish a two-way communication with a Revit context, there was a technical necessity to follow this design. The necessity arises from a DLL collision that occurs when trying to use the xBIM toolkit inside Revit context directly; Microsoft.Extensions.Logging DLL is a common dependency between Revit and xBIM but each ecosystem has a different incompatible version. So, the solution was to run the IFC parsing/loading operations out-of-process with Revit and establish the communication through named pipes.
Ease creation of named pipes on Unix platform
Syslog daemon (with named pipes support) written in golang (for eg. usage in docker images)