When using the default textual output and the SOURCE path is long enough, the output is truncated.
All lines end with a ≈ and are truncated which make the output unusable because it misses the OSV URL entirely.
╭────────────────────────────────────────────────────┬───────────┬─────────────────────────┬───────────────────────────────────┬───────────────────────────── ≈
│ SOURCE │ ECOSYSTEM │ AFFECTED PACKAGE │ VERSION │ OSV URL (ID IN BOLD) ≈
├────────────────────────────────────────────────────┼───────────┼─────────────────────────┼───────────────────────────────────┼───────────────────────────── ≈
│ xxxxx/xxxxx/node_modules/package-lock.json │ npm │ lodash │ 4.17.4 │ https://osv.dev/vulnerabilit ≈
│ xxxxx/xxxxx/node_modules/package-lock.json │ npm │ lodash │ 4.17.4 │ https://osv.dev/vulnerabilit ≈
│ xxxxx/xxxxx/node_modules/package-lock.json │ npm │ lodash │ 4.17.4 │ https://osv.dev/vulnerabilit ≈
│ xxxxx/xxxxx/node_modules/package-lock.json │ npm │ lodash │ 4.17.4 │ https://osv.dev/vulnerabilit ≈
│ xxxxx/xxxxx/node_modules/package-lock.json │ npm │ lodash │ 4.17.4 │ https://osv.dev/vulnerabilit ≈
│ xxxxx/xxxxx/node_modules/package-lock.json │ npm │ lodash │ 4.17.4 │ https://osv.dev/vulnerabilit ≈
│ xxxxx/xxxxx/node_modules/package-lock.json │ npm │ lodash │ 4.17.4 │ https://osv.dev/vulnerabilit ≈
│
I know about the JSON output, but I'd like to have an untruncated textual output too because it is more readable.
When using the default textual output and the SOURCE path is long enough, the output is truncated.
All lines end with a
≈and are truncated which make the output unusable because it misses the OSV URL entirely.I know about the JSON output, but I'd like to have an untruncated textual output too because it is more readable.