netwatchdog
See every device on your network, know what each one actually is — in plain English — and get told the moment something new shows up.
netwatchdog scans your local network, identifies each device (router, phone, TV,
printer, that suspicious no-name smart plug…), and remembers what it saw so it can
flag new arrivals on the next run.
It is read-only: it pings and reads your OS's neighbor/ARP table. No packet capture, no port scanning, no router login.
Example scan (fictional devices). Real output is color-coded by device type.
What it tells you
- Who's here — every device on your LAN, with its IP and hostname.
- What each one is — vendor + a plain category (phone, media, printer, network gear, IoT chip, or Unknown), so the things worth a second look stand out.
- What's new — anything that wasn't on your network last time gets flagged, with advice on what to do about it.
Device identification uses a built-in table for the most-wanted categories and, optionally, the full public Wireshark OUI list (downloaded once, no account).
Install
pip install netwatchdog
Usage
netwatchdog # scan, identify, save/update baseline, print a report
netwatchdog --no-ping # skip the ping sweep (faster, reads existing table)
netwatchdog --no-manuf # don't download the full vendor database
netwatchdog --json # emit the full report as JSON (build your own UI)
netwatchdog -b ~/mynet.json # use a specific baseline file
The first run saves a baseline of what's on your network. Later runs compare
against it and highlight new devices. Your baseline (netwatch_baseline.json)
describes your own LAN and is git-ignored — keep it local.
Tip: give devices a friendly name in the baseline file so future scans read cleanly, and investigate anything marked IoT chip or Unknown that you don't recognize.
Read-only by design
netwatchdog only sends pings and reads the neighbor table your OS already keeps.
It never captures packets, scans ports, or logs into your router. This is a hard
design boundary — see SECURITY.md.
Development
git clone https://github.com/GreenHarvestDev/netwatchdog.git
cd netwatchdog
pip install -e ".[dev]"
ruff check . && ruff format --check . && mypy && pytest
Tests are fully offline — subprocess, psutil, and socket are mocked, so the
suite runs in well under a second. See CONTRIBUTING.md; new
device-identification data and ARP/route format parsers are welcome (with a test).
License
MIT © 2026 GreenHarvestDev
Metadata
Release files for netwatchdog 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| netwatchdog-0.1.0.tar.gz | 19.3 kB | With provenance | Details for netwatchdog-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| netwatchdog-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for netwatchdog-0.1.0-py3-none-any.whl |
Total release size: 35.9 kB
Release files / netwatchdog-0.1.0.tar.gz
| Download URL | netwatchdog-0.1.0.tar.gz |
|---|---|
| Size | 19.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f28f20a1e21fffe52372771b5df794d4054d8f9bbd910ac902f0eee1c01ad0ac
|
|
BLAKE2b-256 checksum How to use checksums |
37455c2d86e9dfbec070903d114480cbb811e834aef968b1ae9346abd7b27a19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 18, 2026.
Transparency logRelease files / netwatchdog-0.1.0-py3-none-any.whl
| Download URL | netwatchdog-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fbfbd0e5e291c09c8871b6fcd53b6bd9f95c92847545151a106215660186ff45
|
|
BLAKE2b-256 checksum How to use checksums |
71657f4de7bf1d0626aa74a3634fef2b7d33b33a307e2984499e4ac74ab508a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 18, 2026.
Transparency logSecurity for netwatchdog 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for netwatchdog-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.