v0.1.2

What's Changed

• Add a root-owned system install mode for sudo portclue by @pbxqdown in #8

Full Changelog: v0.1.1...v0.1.2

v0.1.1

What's Changed

• Report module version for go install builds by @pbxqdown in #4
• Remove README SVGs that GitHub cannot render by @pbxqdown in #5
• Add a terminal demo GIF to the README by @pbxqdown in #6
• Add a checksum-verified install script for release binaries by @pbxqdown in #7

New Contributors

• @pbxqdown made their first contribution in #4

Full Changelog: v0.1.0...v0.1.1

PortClue 0.1.0

PortClue 0.1.0

First public preview of PortClue: a read-only Linux CLI that explains why a TCP port may or may not be reachable locally, using socket, process, firewall, systemd, and Docker evidence.

Install

Download the archive for your architecture plus SHA256SUMS, then:

sha256sum -c SHA256SUMS --ignore-missing
tar -xzf portclue-0.1.0-linux-amd64.tar.gz   # or linux-arm64
sudo install -m 0755 portclue-0.1.0-linux-amd64/portclue /usr/local/bin/portclue
portclue --version

What this release includes

• Overview of local TCP listeners with service identity, bind scope, and owner
• Per-port evidence chain and local exposure verdict (POTENTIAL, NOT_EXPOSED_LOCALLY, UNKNOWN)
• Overview filters: --bind-scope, --source, --min-confidence
• Versioned JSON output for scripts and agents
• Linux amd64 and arm64 archives with checksums

Honest limits (important)

• POTENTIAL means a local path looks allowed; it does not prove public-internet reachability
• Conservative firewall parsing: unsupported nftables/iptables expressions become UNKNOWN
• Host network namespace, TCP-focused prototype; no UDP, Podman, Kubernetes, cloud security groups, or remote scanning
• Use sudo for the most complete process and firewall evidence

PortClue is read-only: it does not connect to the queried port, change firewall rules, stop processes, or run a daemon.

Apache-2.0. Feedback and issues welcome.