Capsuleers.Intel

Capsuleers.Intel — a standalone, cross-platform desktop intel tool for EVE Online. Copy your Local roster or a D-Scan and it tells you, at a glance, who you're up against and how the hostile fleet is composed.

It is the Intel-only sibling of Capsuleers.IA: same clipboard intel features, same look — without the local AI assistant, the language models or the RAG knowledge index. So the download is tens of MB instead of gigabytes, with nothing to set up on first launch.

Want the AI assistant too (skills, fitting, wormholes, PvE… answered with cited sources)? Get Capsuleers.IA, which bundles both the AI and these Intel features.

Screenshots

All pilots, corporations and alliances shown are invented demo data.

Pilot dossier — playstyle, wingmates and recent ships	D-Scan — fleet composition by ship class, offline
Shared links — 24h links with a live countdown

Features

• Local intel — copy EVE's Local window (Ctrl+A, Ctrl+C) and get a per-pilot roster: kills / losses / efficiency, danger rating, archetype tags and a per-pilot dossier (playstyle, frequent wingmates, recently used ships) from capsuleers.app (its own killmail archive, last 90 days; lifetime totals from eve-kill through the site). A summary strip above the list totals alliances / corporations / pilots and lists every detected alliance as a chip (logo + name + pilot count).
• D-Scan analysis — copy a D-Scan and get the composition broken down by ship class, computed 100% offline from the bundled eve-fit-engine SDE (the system is inferred from celestial names).
• Share — turn any intel or D-Scan into a shareable, full-fidelity link (valid 24h) on capsuleers.app; the Site recomputes the canonical payload so the shared page is richer than the local snapshot. Generated links live in the History modal with a live countdown.
• Clipboard watch — an opt-in background watcher detects a Local or a D-Scan the moment you copy it (with an audible cue), so it keeps working while you play fullscreen on another monitor. On Wayland it reads the clipboard via wl-paste (from wl-clipboard) so background copies are seen even when the app isn't focused, falling back to Electron's own clipboard everywhere else (or if wl-clipboard isn't installed).
• Mini mode — shrink to an always-on-top icon; minimize to the system tray.

Nothing leaves your machine except the lookups the features explicitly need: pilot names → ESI and capsuleers.app for Local intel (eve-kill only if the site does not answer), item type IDs already resolved offline, and the raw scan → capsuleers.app only when you press Share. D-Scan analysis is fully offline.

Privacy & security

No account, no telemetry. The renderer runs sandboxed and context-isolated behind a narrow IPC bridge, with a strict Content-Security-Policy (connect-src 'self' → no exfiltration even if a rendering bug occurred) and quote-safe HTML escaping; the packaged binary is hardened with Electron fuses (RunAsNode off, asar-only load) and the full-wipe action requires an explicit confirmation. Details: docs/security-review-2026-06-29.md; report issues per SECURITY.md.

Run from source

Requires Node.js (a recent LTS) on Windows or Linux.

cd desktop
npm install
npm start                 # launches the app

Build installers

cd desktop
npm run dist:linux        # Linux AppImage
npm run dist:win          # Windows NSIS installer (build on Windows)
npm run pack              # unpacked folder, for quick testing

Builds publish to GitHub Releases (electron-updater handles in-app auto-update). For a local build that doesn't publish, the dist:* scripts already pass --publish never.

Continuous build & auto-release (GitHub Actions)

.github/workflows/build.yml runs automatically on every push / merge to main: it builds the Linux AppImage + Windows NSIS installer on their native runners and publishes a GitHub Release with the installers + latest*.yml update manifests (which electron-updater consumes for in-app auto-update). The installers are also attached to the workflow run as artifacts.

The release version is computed at build time as <major>.<minor>.<run-number> from desktop/package.json (e.g. 0.1.0 → release v0.1.42 on run #42), so each release is distinct and monotonically increasing — required for auto-update — without committing a version bump back to the repo. To start a new minor/major line, bump major/minor in desktop/package.json and push to main; the patch keeps tracking the run number.

No secrets to configure: the workflow uses the built-in GITHUB_TOKEN.

Architecture

Electron app, entry point desktop/src/main.mjs. No server, no database, no native modules.

This is the beginning of the README. Read the rest at the original. Read the full README ↗