Perimeter
It tells you what changed on your network, and when it cannot tell.
Every network scanner hands you a table of addresses and open ports. Perimeter reads the table for you, and it is never allowed to call your network quiet while it cannot see.
macOS, command line · 2026Python · nmap · mDNS · SSDP
Example runs. The layout, remedies and verdicts are the tool’s own.
Why
Silence is not the same as safety.
A tool that reports nothing new while it is actually blind is worse than no tool, because you would believe it. So every probe answers with one of five words, and empty is never allowed to mean ok.
okRan, and saw something.
emptyRan cleanly and saw nothing. Ambiguous, and reported as ambiguous.
BLOCKEDFailed for a reason it can name, with the remedy beside it.
skippedNeeds privileges it does not have. Not a failure.
ERRORA bug, not a finding: the network is unknown, not clean.
The first real run
Its first verdict was wrong. Now it checks itself.
Every probe passed, and the verdict was a confident SEEING. But the sweep had found 2 hosts on a network where the ARP cache already knew 6. Now every run checks the probes against each other, and two that disagree bring the verdict down, even when both passed.
Roadmap
Built in epochs, each finished before the next is written.
- 0Can you even see? (done)What this machine can see
- 1Inventory (done)What is on the network
- 1.5Amendments (done)Names, JSON output, CI
- 2IdentitynextDevices, not addresses
- 3Change (planned)What changed, and when
- 4The dispatch (planned)A weekly note in plain words
- 5Linux (planned)The second platform
- 6Release (planned)A licence and a public repo
“Nothing there” and “I cannot see” are different answers.
Free for home use, and no MAC address ever leaves the machine. Windows will warn that the installer is not signed yet: choose More info, then Run anyway.