macOS
brew install vividlocal Homebrew formula metadata
sudo port install vividMacPorts ports tree · sysutils/vivid/Portfile · source: api.github.com
brew / rank 1719
Generator for LS_COLORS with support for multiple color themes. Version 0.11.1 via Homebrew; verified from local package data. Also installable with debian: sudo apt install vivid.
install
brew install vividlocal Homebrew formula metadata
sudo port install vividMacPorts ports tree · sysutils/vivid/Portfile · source: api.github.com
sudo apk add vividAlpine Linux edge package indexes · vivid · source: dl-cdn.alpinelinux.org
sudo apt install vividDebian stable package indexes · vivid · source: deb.debian.org
nix profile install nixpkgs#vividnixpkgs package indexes · pkgs/by-name/vi/vivid/package.nix · source: api.github.com
sudo pacman -S vividArch Linux sync databases · vivid · source: geo.mirror.pkgbuild.com
scoop install main/vividScoop official bucket manifest trees · bucket/vivid.json · source: api.github.com
winget install --id sharkdp.vivid -eWindows Package Manager source index · sharkdp.vivid · source: cdn.winget.microsoft.com
overview
Generator for LS_COLORS with support for multiple color themes
history
vivid is a themeable generator for the `LS_COLORS` environment variable used by color-aware command-line tools. It replaces hand-written ANSI escape-code tables with YAML filetype databases and theme files.
Its place in package culture is the customization layer around `ls`, `tree`, `fd`, `bfs`, `dust`, and similar tools: install one small binary, generate an `LS_COLORS` value, and make a whole shell environment use a coherent color theme.
The vivid changelog records v0.1.0 as the initial version and v0.3.0 as the point where the project was renamed from `dircolors-hd` to `vivid`. That rename also marked the project more clearly as a theme-oriented alternative to classic `dircolors` workflows.
Subsequent releases filled in the practical pieces that make an `LS_COLORS` generator pleasant to package and use: direct RRGGBB colors, better filetype database handling, embedded default themes and config files, XDG config support, previewing, deterministic output, and additional community themes.
By the 0.9 and 0.11 series, vivid had become a maintained Rust CLI with a catalog of common themes, including popular terminal color schemes, and prebuilt release assets for multiple platforms.
vivid's adoption is tied to the spread of modern Rust command-line tools and highly customized shell prompts. The README explicitly names `ls`, `tree`, `fd`, `bfs`, and `dust` as consumers of `LS_COLORS`, which makes vivid useful beyond a single command.
Its theme collection and package availability made it attractive to users who wanted the same color language across file listings, search tools, and disk-usage tools without editing raw ANSI sequences.
Users generate an `LS_COLORS` string from a named or custom theme and export it from their shell startup files. vivid also supports custom filetype databases and custom YAML themes under XDG-style configuration paths.
The separation between filetype database and theme is the core workflow: file classifications can be shared while colors are swapped independently.
vivid is significant because it turns one of the messier Unix environment variables into declarative data. For package nerds, it is a small example of a modern Rust CLI improving an old shell convention without replacing the surrounding tools.
It also connects several popular CLI packages: `fd`, `bfs`, `dust`, `tree`, and GNU or BSD file-listing tools can all benefit once the environment variable is generated.
security posture
narrow executable package without higher-risk signals.
green risk · low confidence · appliance
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Config paths the tool may read or write during local use.
$XDG_CONFIG_HOME/vivid/filetypes.yml$XDG_CONFIG_HOME/vivid/themes/*.yml~/.config/vivid/filetypes.yml~/.config/vivid/themes/*.ymlexecutables
| Command | Kind | Exposure | Note |
|---|---|---|---|
vivid | executable | indexed executable | Discovered from the local executable index. |
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
install metadata
| Package key | brew:vivid |
|---|---|
| Version | 0.11.1 |
| Package manager | Homebrew |
| Homepage | https://github.com/sharkdp/vivid |
| Repository | https://github.com/sharkdp/vivid |
| Bottle | not recorded |
| Service | none declared |
source database matches
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
vivid 0.9.0-3+b2
LS_COLORS manager with multiple themes
https://github.com/sharkdp/vivid
sudo apt install vividvivid
nix profile install nixpkgs#vividvivid 0.9.0-1
LS_COLORS manager with multiple themes
https://github.com/sharkdp/vivid
sudo apt install vividvivid 0.11.1-r0
Themeable LS_COLORS generator with a rich filetype database
https://github.com/sharkdp/vivid
sudo apk add vividvivid 0.11.1-1
LS_COLORS manager with multiple themes
https://github.com/sharkdp/vivid
sudo pacman -S vividvivid
sudo port install vividmain/vivid
scoop install main/vividsharkdp.vivid
winget install --id sharkdp.vivid -esource trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.