Releases
Changelog, immutable by design.
A published version never changes: different bytes always mean a new version number. This page is generated from the same release records that drive downloads.
No releases have been published yet
The first release will be PortWho. Before it ships, the release pipeline has to be in place: a clean Windows build from a tagged commit, SHA-256 checksums, immutable download paths, an honest signed or unsigned status and the owner's approval of the exact files.
Development status
Where each tool stands today.
| No. | Tool | Built and tested internally | Public download | Status |
|---|---|---|---|---|
| 01 | PortWho | 6 of 8 parts | None yet | In development |
| 02 | FileScope | 4 of 6 parts | None yet | In development |
| 03 | Tidy | 5 of 6 parts | None yet | In development |
| 04 | NetDoctor | 5 of 6 parts | None yet | In development |
| Rev | Part | Status |
|---|---|---|
| A1 | Read-only engine IP Helper enumeration, process, service and Authenticode resolution, including exited and reused process IDs. | Implemented |
| A2 | Command line (portwho) Table, details and JSON views with filters. | Implemented |
| A3 | JSON output (schema v1) | Implemented |
| A4 | WPF desktop application (PortWho.exe) Port lookup, filters, details pane, background signature checks, JSON and CSV export. Tested internally; not released. | Implemented |
| A5 | Packaging and release verification Reproducible portable ZIPs with SHA-256 sums, a manifest, an independent verifier and tamper tests. Every package so far is an unsigned internal build. | Implemented |
| A6 | Windows CI Build, format check, tests and an unsigned internal package on every change. | Implemented |
| C1 | Release signing decision No code-signing certificate exists. Free signing is being evaluated; the first x64 release may instead be unsigned, only after an independent rebuild and review and the owner's approval. | Planned |
| C2 | Public release Nothing is published or downloadable. | Planned |
| Rev | Part | Status |
|---|---|---|
| A1 | Inspection engine Content identification, extension check, SHA-256, offline Authenticode, Mark-of-the-Web and findings. Several hundred automated tests, including fuzzed and tampered input. | Implemented |
| A2 | Command line (filescope) Readable output with hidden characters revealed, and JSON (schema v1) for scripts. | Implemented |
| A3 | WPF desktop application (FileScope.exe) Drop, paste or browse for a file; answer first, evidence below. Tested internally; not released. | Implemented |
| A4 | Packaging and release verification Reproducible portable ZIPs with SHA-256 sums, a manifest and an independent verifier. Every package so far is an unsigned internal build. | Implemented |
| C1 | Release signing decision No code-signing certificate exists. Free signing is being evaluated; an unsigned FileScope release would need its own policy decision. | Planned |
| C2 | Public release Nothing is published or downloadable. | Planned |
| Rev | Part | Status |
|---|---|---|
| A1 | Scan, classification and move planner Extension rules, collision detection and a plan identifier that changes whenever the folder does. | Implemented |
| A2 | Journal, recovery and undo Private per-user journal of the last 100 operations; interrupted runs are recognised and checked. | Implemented |
| A3 | Command line (tidy) scan, plan, apply with an approval ID, history, show, undo and recover. | Implemented |
| A4 | WPF desktop application (Tidy.exe) Scan, review, confirm, result and History with undo. Tested internally; not released. | Implemented |
| A5 | Packaging and release verification Reproducible portable ZIPs with SHA-256 sums, a manifest, an independent verifier and tamper tests. Every package so far is an unsigned internal build. | Implemented |
| C1 | Release signing decision and public release Nothing is published or downloadable. No code-signing certificate exists; an unsigned Tidy release would need its own policy decision. | Planned |
| Rev | Part | Status |
|---|---|---|
| A1 | Diagnostic engine Ten-stage general diagnosis and a gaming scenario, each conclusion tied to the observations it rests on. | Implemented |
| A2 | Windows platform (read-only) IP Helper, the DNS client, WinHTTP and sockets; registry keys opened read-only. | Implemented |
| A3 | Command line (netdoctor) diagnose, gaming, adapters and probes, with JSON output. | Implemented |
| A4 | WPF desktop application (NetDoctor.exe) Internet and Gaming pages over the same engine, the probe list before every start, a separate confirmation for the load test and redacted report export. Tested internally; not released. | Implemented |
| A5 | Packaging and release verification Reproducible portable ZIPs with SHA-256 sums, a manifest, an independent verifier and tamper tests. Every package so far is an unsigned internal build. | Implemented |
| C1 | Release signing decision and public release Nothing is published or downloadable. No code-signing certificate exists; an unsigned NetDoctor release would need its own policy decision. | Planned |
- Implemented
- Merged into the main branch and covered by automated tests on Windows. Implemented is not the same as released.
- Planned
- Not started.
- Released
- Nothing yet. No part of this product has been signed or published, and nothing can be downloaded.