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.25.2.
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:
0b624352621df6bc4fc94975dd0225cb03320e36bc28e196b580f60fbf7f1277 npiperelay_windows_386.exe
7958efa1f86bf457c4487e04267c7398991377f7c6929cfed5b1d98a508afcbb npiperelay_windows_386.zip
d7f09eac5a072a93177bd8aa9213616eb66873058c8b9a61b8a1f3d4c1e92ebb npiperelay_windows_amd64.exe
990ca994caf66756a4d6a041a7da75cc6c359d8e2d057e5b34cf4ba3cdb8cdb4 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:
- 1617dce Bump golang.org/x/sys from 0.36.0 to 0.37.0
- 3b2820f Bump golang.org/x/sys from 0.35.0 to 0.36.0
- 4565103 Bump actions/setup-go from 5 to 6
- 7ac9be5 Cleanup golangci-lint configuration
- 831260d Fix spelling in GoReleaser release notes template
(Application executable in release assets built with Go version 1.25.2).