This is a release of my forked project, from branch fork. See below for full changelog, listing all commits since previous fork release. The primary asset of the release is a direct download link for a ready-to-use build of the application's single executable, as well as an alternative .zip archive containing the same executable. It is built with Go version 1.26.5. About this fork This release is from my fork of jstarks/npiperelay, adding some smaller improvements on top of upstream release v0.1.0. The changes are conservative; primary concern is to keep the code updated and secure, considering upstream has not been updated since this first release back in mid 2020. See previous release notes for fork releases starting with v1.0.0 to learn about all changes. Checksums GitHub automatically computes SHA-256 checksums for all release assets, which you can see to the right of the asset names in the "Assets" section below. These are generated at upload time and are immutable. The build system also computes SHA-256 checksums of built executables, and these are published as text file asset npiperelay_checksums.txt. Note that the .zip asset for the amd64 (x64/64-bit) and 386 (x86/32-bit) architectures both contain a single executable with name npiperelay.exe, and it is identical to the .exe asset with same name as the .zip asset, i.e. npiperelay_windows_386.exe and npiperelay_windows_amd64.exe, and should therefore have the same checksum. These are the SHA-256 checksums of all binary release assets, as published in npiperelay_checksums.txt: 6ca75c866b051991b7c56471f78b26028fe4d6a71f95048ae008b77d21f5375b npiperelay_windows_386.exe fe5fe1d15a0181e99526aed04a3f37f19383b75714450379f25e3b57ecb0552c npiperelay_windows_386.zip cea82cf5c9c22a28bef8075750acb7958f766393baebff4597cf21442f71c4b3 npiperelay_windows_amd64.exe c4b48f6868f2eadc546bebab7700e8f217bb46ca36ad91bf57fedbb5254b1633 npiperelay_windows_amd64.zip Antivirus If your local antivirus treats the downloaded archive or executable as suspicious or malicious, you should try to report it as a false positive, e.g. to Symantec on symsubmit.symantec.com (select "Clean software incorrectly detected"). At the time of the release, no security vendors on VirusTotal flagged the asset download urls as malicious, but some very few (well below 10%) did flag the zip archive and executable files themselves (see report for each of the assets in expandable section below). The implementation is less than 300 lines of go code, plus a single, commonly used, third party dependency. The source code is automatically run through vulnerability analysis, using Go's govulncheck and GitHub's CodeQL, and a long list of code quality checks (linters), using golangci-lint (see .golangci.yml for the complete list). If you do worry, you are free to analyse the code yourself, and you can also build the executable locally from source. Changelog Commits since previous fork release:

• c1f3524 Bump golang.org/x/sys from 0.46.0 to 0.47.0
• 444bd10 Bump actions/checkout from 6 to 7 (Application executable in release assets built with Go version 1.26.5).