Problem
The output contains no ANSI colour at all. There is no IsTerminal/isatty check, no NO_COLOR handling, and no escape sequences anywhere in the source.
$ http-assert --assert-ok .../500 2>&1 | grep -c $'\033'
0
Why it matters
The entire point of the output is a verdict, and [+] PASSED / [-] FAILED are distinguished only by one character. Scrolling a CI log, a failure looks exactly like a success. This is the cheapest possible legibility win the tool has available: green on [+], red on [-], and arguably red on the - assertion: … lines.
The sigil vocabulary is already good and the README documents it fully — colour would reinforce it, not replace it.
Suggested fix
Colour [+] green and [-] / Error: red when stderr is a TTY. Honour NO_COLOR and add --color=auto|always|never, defaulting to auto, so CI logs and pipes stay clean.
Problem
The output contains no ANSI colour at all. There is no
IsTerminal/isatty check, noNO_COLORhandling, and no escape sequences anywhere in the source.Why it matters
The entire point of the output is a verdict, and
[+] PASSED/[-] FAILEDare distinguished only by one character. Scrolling a CI log, a failure looks exactly like a success. This is the cheapest possible legibility win the tool has available: green on[+], red on[-], and arguably red on the- assertion: …lines.The sigil vocabulary is already good and the README documents it fully — colour would reinforce it, not replace it.
Suggested fix
Colour
[+]green and[-]/Error:red when stderr is a TTY. HonourNO_COLORand add--color=auto|always|never, defaulting toauto, so CI logs and pipes stay clean.