# Install style-dictionary with Homebrew Build system for creating cross-platform styles. Version 5.5.0 via Homebrew; verified 2026-06-22. ## Install ```sh sudo av install brew:style-dictionary ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install style-dictionary ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:style-dictionary - **Package manager:** Homebrew - **Version:** 5.5.0 - **Source summary:** Build system for creating cross-platform styles - **Homepage:** - **Last updated:** 2026-06-22T14:22:46Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - style-dictionary (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 5.5.0 ## Project history and usage Style Dictionary is a design-token build system and CLI that transforms a shared token dictionary into platform-specific outputs such as CSS, iOS, Android, JavaScript, HTML, and documentation. ### Project history AWS's open source blog says Style Dictionary began inside Amazon and was released publicly on GitHub in the summer of 2017 after an internal presentation led to requests to make the tool available outside the company. The official project documentation now describes Style Dictionary as a build system for exporting design tokens to any platform and notes forward compatibility with the Design Tokens Community Group specification. ### Adoption history The project is distributed as an npm CLI and module, while the input package facts show it is also packaged by Homebrew. That puts it in both JavaScript dependency workflows and system package-manager workflows. Style Dictionary became important as design systems moved token data out of visual design tools and into source-controlled build pipelines that can generate platform-native assets. ### How it is used A typical project keeps token files and a Style Dictionary configuration in the package root, then runs style-dictionary build or calls the Node API to transform and write platform outputs. The official configuration docs say the CLI looks for config.json or config.js by default and supports JSON, JSONC, JSON5, and JavaScript configuration files, with custom transforms, formats, filters, and actions available for advanced builds. ### Why package nerds care Style Dictionary matters to package nerds because it turns design-system data into a build artifact problem: token files in, platform packages and generated source out. It is also a useful case study in CLI packaging across ecosystems. The canonical distribution is npm, but Homebrew packaging makes the command easy to install as a general developer tool. ### Timeline - 2017: AWS says Style Dictionary was released on GitHub in the summer of 2017. - 2020s: The official docs describe forward compatibility with the Design Tokens Community Group format. - 2026: Input package facts list Style Dictionary as a Homebrew formula. ### Related projects - The Design Tokens Community Group specification is a related standard the docs mention. - npm is the primary JavaScript packaging channel documented by the README. ### Sources - - - - - - input.source_facts.package-manager ## Security Notes generalized runtime or code generation signal. - **Geiger risk:** yellow / medium - generalized runtime or code generation signal ## Configuration and credential file locations 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. ## Configuration files - Unix: config.json, config.js ## Combined YAML source View the package source record on GitHub. [combined/style-dictionary.yml](https://github.com/mxcl/pkgdb/blob/main/combined/style-dictionary.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph