Cormorant Fell — WiNGSPAN alumni and, on balance, more of a wormhole enthusiast than a wormhole survivor — built this. It works. It has opinions. Some of them are correct.
Proximity Intelligence Platform · DSS-T3 · Capsuleer Edition
HARUSPEX is a terminal-based EVE Online intel tool — a TUI, meaning it lives in your terminal, runs on keyboard input, and renders entirely in text. This is considered a feature. Run it on a second monitor, alt-tab to it, prop it in a corner — HARUSPEX has no opinion on your window management and is not your Space Mom. You paste things into it. It tells you things about those things. Whether those things are accurate is, per HARUSPEX's own legal counsel, a matter of active philosophical inquiry.
HARUSPEX INTELLIGENCE DIVISION MAKES NO REPRESENTATIONS REGARDING
THREAT ACCURACY, TACTICAL VIABILITY, OR THE DISPOSITION OF PILOTS
NOT ON D-SCAN.
HARUSPEX HAS NEVER LOST A SHIP.
HARUSPEX HAS ALSO NEVER FLOWN ONE.
HARUSPEX CONSIDERS THESE FACTS UNRELATED.
D-Scan ingests the raw output of your directional scanner and returns a structured tactical picture. This happens locally, against a bundled ship database covering 529 hull types, in under a millisecond. No network request is made. The results are therefore equally fast whether you are in Jita or a C5 with no static.
Ships are classified into five tactical categories — ▸ Combat, ◆ Recon, ◎ Logi, ○ Hauler, · Other — each rendered with a proportional bar chart and percentage breakdown. This is the part that tells you roughly what kind of problem you have.
Signals of Interest identifies tactically significant hulls and groups them by category in threat-priority order: Black Ops, Command Ships, Heavy Interdictors, Interdictors, Combat Recons, Strategic Cruisers, Logistics Battleships, and the covert-capable classes. Each category is iconised for rapid scanning. This is the part that tells you specifically what kind of problem you have.
Combat Recon Ships carry a passive role bonus reducing their sensor strength to zero, making them invisible to directional scanners by design. If one nonetheless appears in Signals of Interest, HARUSPEX notes this and considers it significant. HARUSPEX does not speculate as to how.
Field conditions catalogues everything that is not a ship, with annotations where context changes the meaning:
- A Mobile Tractor Unit indicates a pilot currently running a site. They are probably not watching their directional scanner. HARUSPEX considers this tactically relevant.
- A deployed warp disruption probe indicates something is being caught right now.
- A cynosural field indicates that whatever was invited has arrived.
- Combat probes indicate an active hunter. You may be the target. HARUSPEX cannot confirm this but thinks it worth mentioning.
- A MTU alongside wrecks resolves to a more specific annotation than either alone.
The operational assessment synthesises the above: fleet archetype (gate camp, wormhole hunter gang, doctrine fleet, doctrine fleet with ewar wing, black ops drop, capital escalation, nano roam, and others), logistics ratio when it crosses significance thresholds, and an overall threat statement. It is produced by an analyst who has reached these conclusions before and finds them only mildly interesting.
The overview card presents a compressed version of the full analysis — bar chart, signals of interest by category, field condition flags, and all assessment lines — so the picture is legible at a glance before you commit to opening the panel. Pressing d opens the full assessment. Pressing Esc returns you to the overview, where HARUSPEX will continue to hold your results without complaint.
Local accepts a paste of your local chat roster and cross-references every name against the EVE registry and zKillboard's public kill records. It will tell you how many people have died, how dangerous they are assessed to be, and whether any of them are known wormhole affiliates. It will not tell you whether any of them are about to kill you. That information is available elsewhere, typically in the form of a bright flash and a pod notification.
Monitoring watches your EVE chat logs in real time. Any pilot who speaks in local is automatically enriched, assessed, and added to the table without further input from you. The system name is detected automatically and displayed in the header. Pilots who do not speak will not appear. HARUSPEX considers this an upstream limitation and has filed the appropriate documentation.
Pre-compiled binaries are available on the Releases page for macOS (universal), Linux, and Windows. No Python required. No assembly required. No explanation of what a wormhole is required.
Each release ships as an archive containing a haruspex/ directory. The binary inside is named haruspex (or haruspex.exe on Windows). The _internal/ folder next to it contains the bundled Python runtime — it must stay alongside the binary. You never need to touch it.
tar -xzf haruspex-macos.tar.gz
xattr -dr com.apple.quarantine haruspex/
./haruspex/haruspexxattr clears the Gatekeeper quarantine flag applied to all downloaded files. HARUSPEX is not a threat. Gatekeeper has been informed. It remains unconvinced.
To install system-wide:
sudo mv haruspex /usr/local/lib/
sudo ln -s /usr/local/lib/haruspex/haruspex /usr/local/bin/haruspexThen run haruspex from any terminal.
tar -xzf haruspex-linux.tar.gz
./haruspex/haruspexTo install system-wide:
sudo tar -xzf haruspex-linux.tar.gz -C /usr/local/lib
sudo ln -s /usr/local/lib/haruspex/haruspex /usr/local/bin/haruspexThen run haruspex from any terminal.
Extract haruspex-windows.zip. Run haruspex\haruspex.exe from a terminal (Command Prompt or PowerShell). Double-clicking may work, but a terminal window is required for the interface to render. If Windows Defender objects, click "More info" → "Run anyway". HARUSPEX has noted this is not an ideal onboarding experience.
To install system-wide: add the extracted haruspex\ folder to your system PATH. Then run haruspex from any terminal.
If you have Python 3.11+ and uv installed, this is the cleanest option — no archives, no PATH wrangling, and uv tool upgrade haruspex to update:
uv tool install git+https://github.com/mogglemoss/haruspex
haruspexRunning from source — requires Python 3.11+ and uv:
git clone https://github.com/mogglemoss/haruspex
cd haruspex
uv sync
uv run haruspexHARUSPEX requires no configuration for D-Scan and Local. It knows what it needs to know. Live log monitoring is opt-in, on the reasonable grounds that reading your files without permission would be rude.
Create ~/.config/haruspex/config.toml to enable it:
[logs]
enabled = trueHARUSPEX will auto-detect your EVE log directory on macOS, Linux (Steam/Proton), and Linux (Steam Flatpak). On Windows, the directory must be specified manually, because Windows remains, as ever, a place where things must be specified manually:
[logs]
enabled = true
path = "C:/Users/YourName/Documents/EVE/logs/Chatlogs"Log monitoring is TOS-compliant. CCP writes these files specifically for third-party tool consumption. HARUSPEX is a third party. CCP has not objected to this characterisation. This situation may continue indefinitely.
Flagged corporations and alliances — HARUSPEX ships with a small built-in list of known wormhole-active groups. You may add any corporations or alliances you want highlighted — rivals, locals, groups of interest, entities HARUSPEX should know about for reasons HARUSPEX will not enquire into:
[logs]
enabled = true
wh_corps = ["that alliance", "those people from last tuesday"]
wh_alliances = ["the coalition we don't talk about"]Entries are matched as case-insensitive substrings. They do not have to be wormhole-related. HARUSPEX does not judge your associations. HARUSPEX has noted them.
| Key | Action |
|---|---|
d |
D-Scan panel |
l |
Local intel panel |
m |
Monitoring panel |
Esc |
Return to overview |
c |
Copy intel summary to clipboard |
? |
Help overlay |
Ctrl+R |
Clear current panel |
q |
Quit |
From the overview, c copies a combined summary of all three panels simultaneously. HARUSPEX has prepared this text. Whether you paste it into fleet chat is between you and your fleet commander.
Clicking any overview card opens that panel. This works as expected. HARUSPEX is pleased by this.
| Component | Detail |
|---|---|
| D-Scan engine | Local · bundled SDE corpus · no network |
| Hull coverage | 529 types · 46 groups · drone classes |
| Signals of Interest | 40 flagged hulls · 10 tactical categories · threat-priority order |
| Fleet archetypes | 8 detected types · gate camp · WH gang · doctrine fleet · black ops · capital · and others |
| Field conditions | MTU · deployed bubble · cyno field · combat probes · core probes · wrecks · and others |
| Threat model | Empirical · ship count · logistics ratio · hull composition |
| Name resolution | ESI /universe/ids/ · bulk |
| Kill data | zKillboard public API · rate-limited · 3 concurrent |
| Danger threshold | ≥50% danger ratio AND ≥10 kills |
| Log format | UTF-16LE · 1 s poll interval |
| Network required | D-Scan: no · Local + Monitoring: yes |
| Auth required | None · public APIs only |
| Source | Purpose | Auth |
|---|---|---|
Bundled ships.json |
Ship name → class/group | None |
ESI /universe/ids/ |
Bulk name → ID resolution | None |
ESI /characters/{id}/ |
Corp and alliance details | None |
| zKillboard API | Character kill statistics | None |
~/Documents/EVE/logs/ |
Live chat log tailing | Local read |
| Platform | Binaries | Log Auto-Detection |
|---|---|---|
| macOS | Universal (arm64 + x86_64) | Yes |
| Linux (native) | Yes | Yes |
| Linux (Steam/Proton) | Yes | Yes |
| Linux (Steam Flatpak) | Yes | Yes |
| Windows | Yes | Set path in config |
HARUSPEX produces assessments, not facts. A pilot with zero kills on zKillboard may be a peaceful hauler. They may also be a veteran with a private killboard and a deep personal commitment to your destruction. HARUSPEX cannot tell the difference. Neither can you, most of the time, which is at least a shared limitation.
A clean D-scan does not mean the system is empty. It means the system appears empty to your directional scanner. These are related but not identical conditions. HARUSPEX has opinions about this distinction and has incorporated them into its threat model, to the extent that a threat model can have opinions.
The system is most useful when combined with spatial awareness, good intel habits, and the kind of quiet suspicion that wormhole space instills in those who survive it long enough to develop opinions.
Fly accordingly.
MIT — see LICENSE
Built with Textual. Uses the EVE Online ESI API. Not affiliated with or endorsed by CCP Games. EVE Online and all related marks are the intellectual property of CCP hf.
— Cormorant Fell, probably in a wormhole