Last 12 weeks · 6 commits
4 of 6 standards met
Summary Closes #49 Remove from the default install graph and load it only when the GIF APIs are used. This keeps and unchanged for static image consumers, while avoiding the old audit chain in default installs. Changes move from to an optional peer dependency lazy-load inside throw a clear error if a GIF API is used without installed document the optional requirement in the type declarations Verification shows it is not installed by default
Summary currently installs as a normal dependency even for consumers that only use / for static images. That ends up pulling this chain into every install: old old -> In consumers that run in CI, this causes installs of to fail audit even when GIF support is never used. Why this matters For static-image-only consumers, GIF rendering is not part of the exercised code path, but the transitive audit findings still apply to the default install graph. Suggested fix Make optional and load it only from / . That would keep the current static image APIs unchanged while removing the vulnerable GIF stack from the default install path. A small follow-up PR is coming with exactly that approach.
Repository: sindresorhus/terminal-image. Description: Display images in the terminal Stars: 1129, Forks: 29. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Topics: cli-utility, image, nodejs, npm-package, terminal-image. Latest release: v5.0.1 (1mo ago). Open PRs: 0, open issues: 0. Last activity: 1mo ago. Community health: 71%. Top contributors: sindresorhus, Richienb, Whoaa512, cbrunnkvist, Baidaly, BendingBender, splars.