Skip to main content

iotaudit

CI License: MIT Python 3.10+ PyPI

Support my open-source work: get a SkinToScan pack
If you find this useful, you can support me by getting a SkinToScan pack, my other project. It's a one-time purchase that directly funds my open-source work.

Buy Single Picture Check, €4.49 Buy 5 Picture Pack, €19.99 (popular) Buy 15 Picture Pack, €54.99

iotaudit is for anyone who wants a straight answer about their own smart-home devices: cameras, plugs, feeders, bulbs, doorbells, and the rest. It watches what a device does on your network and gives each one an A-F grade, a one-line safety verdict, and a one-page HTML report. Everything runs locally: no account, no telemetry, no cloud.

I wrote it for the cheap gadgets that end up on a home Wi-Fi. The questions are usually the same: who does it talk to, is that traffic encrypted, are any surprising ports open, and did anything change since last time.

Install

pipx install iotaudit

Capturing traffic needs root (sudo). An optional port scan needs nmap. PDF export and the MCP server are extras: pip install "iotaudit[pdf]" and pip install "iotaudit[mcp]". More install notes, including how to get iotaudit onto macOS sudo's PATH, are in the usage guide. Country lookups use a bundled DB-IP Lite database; iotaudit geoip update installs a newer monthly file.

Quick start

One command asks you to confirm this is your network, finds devices, runs the safe checks, captures passively, and writes the report:

sudo iotaudit auto

Files land in ~/iotaudit/YYYY-MM-DD/ as HTML and JSON (and a PDF if that extra is installed). If you already have a capture from Wireshark, your router, OpenWrt tcpdump, or PCAPdroid, analyse it without root:

iotaudit analyze capture.pcap

A step-by-step capture from an OpenWrt router (tcpdump over SSH, then iotaudit analyze) is in the OpenWrt guide.

Skip the typed confirmation with --i-own-this-network once you already know this is your network. To pull one device's traffic through this computer, use ARP or hotspot mode. See capture modes.

What it does

  • A one-line verdict next to the grade. Open ports, public DNS (including DNS-over-TLS and DNS-over-HTTPS), TLS or plaintext, and destination countries are observed facts. Video, audio, and other traffic patterns stay indicators with a confidence.
  • Who the device talks to: domains (DNS, TLS SNI, HTTP Host), IPs, country, organisation.
  • Encryption: plaintext HTTP, unencrypted TCP, old TLS, or high-entropy "custom" protocols.
  • Optional nmap port scan with risk notes, a read-only UPnP port-forward list, an idle-upload check, and a traffic timeline.
  • Offline known-issue hints when a banner matches a curated CVE. A hint changes the grade only in a narrow case; details are in device profiles.
  • Turn a saved audit into a shareable profile draft with iotaudit profile export (see device profiles).
  • iotaudit diff (and --compare) to see what changed since the last audit.
  • For scripts, --summary-json prints a compact grade summary on stdout, and --fail-under B exits 1 when the worst grade is worse than B.
  • HTML and PDF reports, CSV or Markdown export, and --redact when you want to share a report without local addresses.
  • Grades can go into Home Assistant over MQTT (--ha-mqtt, with discovery so sensors appear without YAML) or as a JSON file (--ha-json). See the Home Assistant guide.

Current release is 0.1.25. A sample report and a short demo are on the report page. A full vulnerability feed is still on the roadmap.

iotaudit auto demo (sample data)

MCP server

pip install "iotaudit[mcp]"
iotaudit-mcp

This starts a local MCP server (stdio) so a client on your machine can run the same audit tools. diff_results compares two saved JSON audits the same way iotaudit diff does. The server is listed on mcpservers.org and the official MCP Registry. Tool list and options: MCP server.

iotaudit only audits your own network and your own devices. It refuses non-private targets and requires --i-own-this-network or an interactive I OWN THIS NETWORK confirmation. ARP or NDP spoofing on a network you do not own may be illegal. All data stays local. There is no telemetry.

Findings are indicators based on observed traffic, not proof of wrongdoing by any vendor. IP geolocation by DB-IP. MIT licensed.

Docs

Metadata

Release files for iotaudit 0.1.25

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for iotaudit 0.1.25
File Size Uploaded Provenance Actions
iotaudit-0.1.25.tar.gz 6.1 MB With provenance Details for iotaudit-0.1.25.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for iotaudit 0.1.25
File Interpreter ABI Platform Actions
iotaudit-0.1.25-py3-none-any.whl Python 3 none any Details for iotaudit-0.1.25-py3-none-any.whl

Total release size: 10.9 MB

Release files / iotaudit-0.1.25.tar.gz

Download URL iotaudit-0.1.25.tar.gz
Size 6.1 MB
Tags Source
SHA-256 checksum
How to use checksums
386809c658697442ac322008c0377cbce523a6bad320e33cfaf8cb0f140b093b
BLAKE2b-256 checksum
How to use checksums
af7a2b3ce72f0cef780c68caf16f093ba53e40316c1f1942e10c6fdb4447cddd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 18, 2026.

Transparency log

Release files / iotaudit-0.1.25-py3-none-any.whl

Download URL iotaudit-0.1.25-py3-none-any.whl
Size 4.8 MB
Tags Python 3
SHA-256 checksum
How to use checksums
ba7c2ee2cc3d7236e802ae323d730b571c0283a162512596f3c4af4da2f2d6d7
BLAKE2b-256 checksum
How to use checksums
ca49c58aa35409527d63411814542e9f66b4f07d15cd0d54ad26e68a5b97c832
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 18, 2026.

Transparency log

Security for iotaudit 0.1.25

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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for iotaudit-0.1.25.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 Nov 18, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page