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.27.1. 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: 3a207ec6e59c86dcf7806bfe4d2b5102aee8067c79a45ded75032651925bb49a npiperelay_windows_386.exe a13700a3a491f329b4c2e31c2ab3efb72f60011c01b0f2044b2b7475e2e80aed npiperelay_windows_386.zip dbb448aea38835a65e2e10d83e2dd770a8e4dfa5f43b5669d7551a3125445ca4 npiperelay_windows_amd64.exe f57695f9abee6d68f9079feb6bc22640a183ff49908975a668740caf4ed356e5 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:

• (none, release was created only to build with new Go version) (Application executable in release assets built with Go version 1.27.1).