{"ecosystem":"npm","package":"supports-color","version":null,"bugs":[{"id":162,"ecosystem":"npm","package_name":"supports-color","affected_version":null,"fixed_version":null,"bug_id":"github:88","title":"Give TERM=dumb Higher Priority","description":"Emacs `M-x shell` runs the shell in an environment where the `TERM` variable is set to `dumb`, which informs the shell and applications that the terminal does not support any terminal control escape sequences.\r\n\r\nWhile you have code to handle the [dumb](https://github.com/chalk/supports-color/blob/c94d6c51f60759f72a93d7c73c99e18dae995d73/index.js#L115) setting, both the Windows platform processing and the `TERM_PROGRAM` are processed first.\r\n\r\nFor instance on macOS,\r\n```bash\r\n$ cd /path/to/mocha/node_modules\r\n$ TERM=dumb node -e \"var tty = require('./supports-color'); console.log(tty.stdout);\"\r\n{ level: 2, hasBasic: true, has256: true, has16m: false }\r\n$ TERM_PROGRAM= TERM=dumb node -e \"var tty = require('./supports-color'); console.log(tty.stdout);\"\r\nfalse\r\n```\r\n\r\nMocha is getting publicly blamed for [this](https://emacs.stackexchange.com/questions/27218/why-is-there-so-often-ugly-output-in-node-js-compilation-buffers). Suggestions?\r\n","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/supports-color/issues/88","labels":["bug","help wanted"],"created_at":"2026-04-19T04:30:32.934776+00:00","updated_at":"2026-04-19T04:30:32.934776+00:00"},{"id":161,"ecosystem":"npm","package_name":"supports-color","affected_version":null,"fixed_version":null,"bug_id":"github:114","title":"supportsColor() should recheck process.env.FORCE_COLOR","description":"At the moment, the `supportsColor()` function does not consider all the environment variables fresh each time it's called. This means changing `process.env.FORCE_COLOR` at runtime has no effect on the `supportsColor()` result.\r\n\r\nThis bug prevents us from being able to do `process.env.FORCE_COLOR = '1'`, run a snapshot test of something that uses `chalk`/`supports-color` for formatting, then revert the `FORCE_COLOR` back again.\r\n\r\nThis issue probably blocks a fix for https://github.com/babel/babel/issues/12442 .","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/supports-color/issues/114","labels":["bug","help wanted"],"created_at":"2026-04-19T04:30:32.933809+00:00","updated_at":"2026-04-19T04:30:32.933809+00:00"},{"id":160,"ecosystem":"npm","package_name":"supports-color","affected_version":null,"fixed_version":null,"bug_id":"osv:MAL-2025-46981","title":"Malicious code in supports-color (npm)","description":"The package was compromised and malicious code added.\n\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: ghsa-malware (52d7b5f7535b1ec1964ec7f0a7019898a143639f62bf70f6a5e6b9e2ca580c12)\nAny computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.\n","severity":"medium","status":"open","source":"osv","source_url":"https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised","labels":["GHSA-pj3j-3w3f-j752"],"created_at":"2026-04-19T04:30:32.521504+00:00","updated_at":"2026-04-19T04:30:32.521504+00:00"}],"total":3,"_cache":"miss"}