Repository navigation
Installation
To try NetworkScanner without building it, download the file for your OS from the Releases page.
| OS | File | How to run |
|---|---|---|
| Windows | NetworkScanner-win-Setup.exe |
Run the installer. |
| Windows (portable) | NetworkScanner-win-Portable.zip |
Unzip and run the executable — no install. |
| macOS | NetworkScanner-osx-Setup.pkg |
Run the installer. |
| macOS (portable) | NetworkScanner-osx-Portable.zip |
Unzip and run the .app. |
| Linux | NetworkScanner.AppImage |
chmod +x NetworkScanner.AppImage then run it. |
| CLI (headless) |
netscan-<version>-linux-x64.tar.gz, …-osx-arm64.tar.gz, …-win-x64.zip
|
Command-line scanner for servers / SSH / automation. See Command-Line Interface. |
The
*.nupkg,RELEASES*,assets.*.json, andreleases.*.jsonfiles you may also see in the Release assets are internal files for Velopack's auto-update feed — you don't need to download them.
The installers are not code-signed / notarized yet, so on first launch the OS may show a warning. These are false positives — see Troubleshooting & FAQ for how to get past them:
- Windows — SmartScreen "Windows protected your PC": click More info → Run anyway.
- macOS — "can't be opened": right-click (Control-click) → Open, then Open again.
- Antivirus (e.g. AhnLab V3) may quarantine the installer because it bundles the Velopack auto-updater. Use the Portable (zip) build to avoid this, or restore + exclude the file.
The installed app checks GitHub Releases for newer versions and offers an Update button (via Velopack). Your settings and scan results are preserved across updates because user data is stored in a per-user directory, not the app folder — see Configuration & Data Files.
Prefer to build it yourself? See Building from Source.