v1.12.1

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).

v1.12.0

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.0.

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:

e18b9f5573cb37a1793dfad7731b565c30c6eceda9b7969f20155a9f9d00eaab  npiperelay_windows_386.exe
e24b6eae150deac9ea8d993afaf929b51ee026bd58aaddc9ad3750aad3f4e0bc  npiperelay_windows_386.zip
b7d7dfd101768cd072ec7138f02eb9fa252dceb0c2a091a198cd339667e49724  npiperelay_windows_amd64.exe
9d59e1a1b9546a1a6cd205651e164327fbdc65e3dd0e1b2aa02173d6754e5f39  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:

• c823cbf Bump go version to build with 1.27 while still supporting 1.26
• 571a8b5 Bump actions/setup-go from 6 to 7

(Application executable in release assets built with Go version 1.27.0).

v1.11.4

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).

v1.11.3

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.4.

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:

27d07c1eb77f79983f0926d97f1bf643949fd5ce48b1f3f38c2e1ac44f84c5c9  npiperelay_windows_386.exe
088bd60906842b0a79b28ef82fa9374a0f740f943fd58b3ca131e6840550d26f  npiperelay_windows_386.zip
81cfeec4f385b1a3b10b734b1eccfb19e4a81a5c7f0fde8108217627edefdbdd  npiperelay_windows_amd64.exe
ff25007805cba339646e50f12492b41d824e91be212f3b57ab648dec24919c7d  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:

• 8d70f70 Bump golang.org/x/sys from 0.45.0 to 0.46.0
• e8b10e5 Bump golang.org/x/sys from 0.44.0 to 0.45.0

(Application executable in release assets built with Go version 1.26.4).

v1.11.2

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.3.

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:

4c024bf25d9024193642177e5c73cdf7db57a39b981def15086c299098146f44  npiperelay_windows_386.exe
40b2a30046013017fbf6390f94e6905fac7b2f40c4176013a50faad9254d4e28  npiperelay_windows_386.zip
10bac79493deadd0fdfea3d085046497b2beba132c4ba3042b3bedc7bb9f7c1c  npiperelay_windows_amd64.exe
cbf81e62f09a814141c27e1ff7f09f5cb142539643c6e197b4f6350b9e3581bd  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:

• 65ebdfd Bump golang.org/x/sys from 0.43.0 to 0.44.0
• 76d69d2 Bump golang.org/x/sys from 0.42.0 to 0.43.0

(Application executable in release assets built with Go version 1.26.3).

v1.11.1

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.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:

a40ac1ec74e871185c0063d1d697d68c34458ea4ee47e544c1fc5d3f2cbd5c02  npiperelay_windows_386.exe
0873cfbcada084be4315dd7662f8af33955187b5e458322b9048c50208a0ca52  npiperelay_windows_386.zip
78ce62f603f888cbe70663aaee5e9094be1a9bc64d92cad6d3953cc2b32680e0  npiperelay_windows_amd64.exe
bdaff90463aa63b60f7e74eee00a169a51b211a541343bb8f0b98b2fb5d7f348  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:

• 1d018cd Bump goreleaser/goreleaser-action from 6 to 7
• 992fd37 Bump golang.org/x/sys from 0.41.0 to 0.42.0

(Application executable in release assets built with Go version 1.26.2).

v1.11.0

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.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:

fa69c4d98407aa786a93931fed66887647fdd767f90db439f984f73780942830  npiperelay_windows_386.exe
c96e340ddd855d5ac5a1cbdc4fd5660533c44fd4cc9a9461fce33ebebbbb8085  npiperelay_windows_386.zip
01b71bd8e4f18e2750aa0876cb7103ade756cdb3a8a296d5219910241138a6d6  npiperelay_windows_amd64.exe
9d3ce6223f1d167eb019dfd44ff3244778d3863b6541632a643b416bd6090d61  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:

• 1d018cd Bump goreleaser/goreleaser-action from 6 to 7
• 992fd37 Bump golang.org/x/sys from 0.41.0 to 0.42.0

(Application executable in release assets built with Go version 1.26.1).

v1.10.0

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.0.

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:

51b5c26ac7ce5b494dff6b75960eb895b8bd9c5f8bb40db40e512c6f42144c5b  npiperelay_windows_386.exe
dbc640749cebc2abebfd95114b22e82d4b2b6d0873875c04f526443372075f89  npiperelay_windows_386.zip
55d6900a174f91b55c7132c909af641eefdefb410cdc65f8bb0a57705d84f841  npiperelay_windows_amd64.exe
81af7bcdafc53ed80f6e8977f447e66008f3eed65a66ea55bcb83ae405087fff  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:

• 23d6c10 Fix GoReleaser deprecated properties
• d77bf2f Bump go version to build with 1.26 while still supporting 1.25
• b5beca7 Bump golang.org/x/sys from 0.40.0 to 0.41.0

(Application executable in release assets built with Go version 1.26.0).

v1.9.3

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.7.

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:

0cdd591a75a899987237c568260c2068b54f3e05a74894eb2f7ea4745254f314  npiperelay_windows_386.exe
d0a896b7c96cdfe2a8ce4ff24a52f884ae2c4472582dfaa12fb4eb32f31c5ebc  npiperelay_windows_386.zip
4884cfd321bc8da63b1be01394f0ce6ddffe21c28ffdf6d418bebf247206aa73  npiperelay_windows_amd64.exe
8202341079af82c38160534765ef03dddd6e9b095844c569424f7a07e231e47b  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:

• 6dc2247 Bump golang.org/x/sys from 0.39.0 to 0.40.0

(Application executable in release assets built with Go version 1.25.7).

v1.9.2

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.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:

5c8f8afe0e3307cbd0442ff828fdfdf487938927069e54d7b69194d1af7ee2db  npiperelay_windows_386.exe
ea8d1df3dd20c92a4b20496f048221e92468d76fed87f1c426fee99ac8e5f410  npiperelay_windows_386.zip
0be2e7df371ad7207fb9d804d302128ca35c5bd75eace8330eb2bbe294902d87  npiperelay_windows_amd64.exe
e33c7f166b633cc0019c461da43245bf74ca454bd56f5aaf09514bbadd76efb5  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:

• 02567b7 Bump golang.org/x/sys from 0.38.0 to 0.39.0
• 42ce80a Bump actions/checkout from 5 to 6
• a2d6af3 Bump golangci/golangci-lint-action from 8 to 9
• 60cb164 Bump golang.org/x/sys from 0.37.0 to 0.38.0
• bd85194 Bump github/codeql-action from 3 to 4

(Application executable in release assets built with Go version 1.25.5).