PortAura is a native macOS utility that shows which processes are listening on which ports, where they’re exposed, and what has changed since your trusted baseline. It helps you understand local services without digging through Terminal commands. Everything runs locally on your Mac.
I built PortAura because I kept running into the same question on my Mac: what is actually listening on this port, which process owns it, and is this something new?
Terminal tools can answer that, but the information is scattered and not always easy to read at a glance.
PortAura brings ports, processes, exposure scope, and baseline changes into one native Mac interface. A baseline change doesn’t automatically mean risk — it simply gives you a clear signal that something changed and is worth reviewing.
Everything runs locally on your Mac. No account, no cloud dashboard, and no unnecessary background service.
I’d really appreciate feedback from Mac users and developers on what would make this more useful.
appreciate that this stays local instead of shipping port/process data to a cloud dashboard - for a security tool that's the right default. curious how the baseline gets set initially though: is it a manual "snapshot now" action, or does it auto-baseline after first install, since a bad first snapshot (taken while something unwanted is already running) would make the whole diff useless.
Report
Maker
@galdayan Good question — PortAura does not auto-baseline on first install.
The baseline is only created when the user explicitly reviews and confirms the current listening state, and updating it later also requires confirmation. That’s intentional for exactly the reason you pointed out: I don’t want the first snapshot to be silently treated as trusted.
That said, PortAura is a change detector rather than a malware scanner, so if someone manually confirms a bad state, it would still become part of the baseline. Your point makes me think the first-baseline flow should probably make that trust decision even more explicit. Thanks for calling it out.
Dial
appreciate that this stays local instead of shipping port/process data to a cloud dashboard - for a security tool that's the right default. curious how the baseline gets set initially though: is it a manual "snapshot now" action, or does it auto-baseline after first install, since a bad first snapshot (taken while something unwanted is already running) would make the whole diff useless.
@galdayan Good question — PortAura does not auto-baseline on first install.
The baseline is only created when the user explicitly reviews and confirms the current listening state, and updating it later also requires confirmation. That’s intentional for exactly the reason you pointed out: I don’t want the first snapshot to be silently treated as trusted.
That said, PortAura is a change detector rather than a malware scanner, so if someone manually confirms a bad state, it would still become part of the baseline. Your point makes me think the first-baseline flow should probably make that trust decision even more explicit. Thanks for calling it out.