NetworkWright
Self-hosted network monitoring and automation for small network teams. Device-centric monitoring (replacing PRTG/Orion-style sensor sprawl), config backup, IPAM, and safe, approved bulk changes with automatic rollback.
Offline by design. NetworkWright makes zero outbound connections. Everything it needs ships in a signed offline bundle; GitHub is only where source and releases live.
Status: pre-alpha. Phases 1-8 done, plus phase 9 (config compliance rules, software end-of-life tracking, network map, NetBox import, suggested fixes for alerts): foundations, inventory, monitoring collection, alerting, config backup, IPAM and VLANs, device page (web UI), safe bulk changes. Feature-complete for a first release; release-readiness work (account management, migrations, signed bundles) done; not yet tested on real devices (see docs/lab-test-plan.md). Not ready for production use.
What exists today (phase 1)
-
Local accounts with Argon2id passwords, mandatory TOTP, lockout, replay protection
-
Roles: viewer / engineer / admin
-
Hash-chained, tamper-evident audit log
-
CredentialProviderinterface with a local AES-256-GCM provider -
Docker Compose stack (TimescaleDB, API, worker, alerter, executor) on an internal-only network
-
Offline bundle scripts and a CI test that fails on any outbound connection
-
Inventory: identity by serial first, management address second; conflicting records are rejected
-
Discovery holding list: nothing enters inventory until an engineer approves it
-
Search by hostname, serial, site, platform, address or CIDR
-
Bulk import from CSV, JSON or YAML with a dry run, per-row errors and whole-batch rollback
-
SNMP v2c/v3 polling: bandwidth, errors, CPU, memory, temperature, BGP/OSPF state, LLDP/CDP topology, ICMP
-
Port classes (trunk/routed = critical, access = user) with engineer overrides; adjustable poll intervals
-
Worker egress limited to management networks by a host firewall rule, tested in CI
-
Alerting: settle delay, LLDP/CDP dependency suppression, flap damping, maintenance windows, thresholds
-
Email via your internal relay only (STARTTLS, internal CA), outbox with retries; escalation and acknowledgement
-
On-call from manual shifts or an internal iCalendar feed (Exchange, CalDAV export); manual swaps win
-
Config backup over SSH: daily and on demand, secrets redacted before storage, version history and diffs, SSH host keys pinned on first contact (a changed key stops backups and raises an alert)
Name
The project is NetworkWright; NetWrkWright is an accepted alternate spelling. The command is networkwright (short form nww). pip install netwrkwright installs the same thing via a tiny pointer package (packaging/netwrkwright).
Quick start (development)
python3 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest -q
Layout
| Path | Purpose |
|---|---|
networkwright/auth |
passwords, TOTP, roles, login service |
networkwright/credentials |
CredentialProvider + local AES-256-GCM provider |
networkwright/audit.py |
hash-chained audit log |
networkwright/collectors |
SNMP client, poller, scheduler, ICMP, worker |
networkwright/alerting |
alert engine, suppression, on-call, email |
networkwright/backup |
SSH fetch, redaction, versions |
networkwright/definitions |
per-platform YAML (health OIDs) |
networkwright/api |
FastAPI app |
deploy/ |
Dockerfile, compose stack |
scripts/ |
offline bundle (build, sign, verify), release key, egress test |
docs/ |
design and security notes |
Later phases add engine, notify, orchestrator, executor, backup,
ipam, definitions, jobs and web.
Licence
Not yet chosen (Apache-2.0 or AGPL-3.0 under consideration). No licence is granted until a LICENSE file is added.
Metadata
Release files for networkwright 0.0.1
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 |
|---|---|---|---|---|
| networkwright-0.0.1.tar.gz | 177.0 kB | Without provenance | Details for networkwright-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| networkwright-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for networkwright-0.0.1-py3-none-any.whl |
Total release size: 330.2 kB
Release files / networkwright-0.0.1.tar.gz
| Download URL | networkwright-0.0.1.tar.gz |
|---|---|
| Size | 177.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bcfaf17c316832fd9e4111e65acfed93a1fdf56b3d86f135c25268f13b13a1a1
|
|
BLAKE2b-256 checksum How to use checksums |
dab1352265fc398353153c4ae8fec65d0649f760d54867ed710cbf11381effe7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Release files / networkwright-0.0.1-py3-none-any.whl
| Download URL | networkwright-0.0.1-py3-none-any.whl |
|---|---|
| Size | 153.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66f18cdff4cdb71dec846dc63e5c919903921aa8d086e8988e169560997fe4fa
|
|
BLAKE2b-256 checksum How to use checksums |
5701cbd3b94fe83b35d8b1bcd624fbb4f6212ba1dca325a2361d9bfeeedf4c04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Security for networkwright 0.0.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.