← Projects
CLI

incidents-cli

Which of the services you depend on are declaring trouble right now: vendor status pages in one terminal view

New releasev0.7.14 days ago
Started
Last change
Licence
MIT

Features

It reads each vendor's own status page, worst first, and tells you what they have declared. A green row is not proof your calls work; a page it cannot read is shown as ? unreadable and counts as not green, never as fine.

  • One view of every vendor — a list worst first, or a board with a card per service in trouble and the healthy ones in a grid
  • Honest about gaps — an unreadable page is never shown as fine, and fails the exit code
  • Watch mode — polls every few minutes and prints a line, or runs a command, only when a status changes
  • Scriptable — --json on every form, meaningful exit codes, static output whenever there is no TTY
  • Configurable — 21 built-in services, plus any Statuspage, RSS feed or plain link you add

The board: a filter column that doubles as the tally, a card per service in trouble, the healthy ones a line each

The list (v): every service, worst first, with a preview of the selected one

One service in detail: open incidents, affected components, earlier ones

▶ Watch the 54-second demo, recorded from the real CLI on invented services. Music: "Nightfall" by Beat Mekanik, CC BY 4.0.

Install

npm install -g @kud/incidents-cli

Node 22 or later.

Written about in…