# Install taze with Homebrew, Nix Modern cli tool that keeps your deps fresh. Version 19.16.0 via Homebrew; verified 2026-07-23. Also installable with nix: nix profile install nixpkgs#taze. ## Install ```sh sudo av install brew:taze ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install taze ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#taze ``` Evidence: nixpkgs package indexes: pkgs/by-name/ta/taze/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:taze - **Package manager:** Homebrew - **Version:** 19.16.0 - **Source summary:** Modern cli tool that keeps your deps fresh - **Homepage:** - **Repository:** - **Last updated:** 2026-07-23T03:40:21Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - taze (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 19.16.0 ## Project history and usage taze is an npm-oriented dependency update CLI that checks and updates JavaScript package versions while defaulting to package.json version ranges. ### Project history The repository was created in 2020 and the README identifies taze as a modern CLI tool for keeping dependencies fresh. It explains the name as Persian for fresh and credits Anthony Fu in the MIT license notice. The README places taze in the same problem space as npm-check-updates and npm-check, while emphasizing a different balance: monorepo support, npx usage without installation, and safe-by-default updates inside allowed version ranges. ### Adoption history By 2026 the official GitHub repository metadata showed several thousand stars and more than one hundred forks, and the input metadata listed Homebrew and Nix packages. Its adoption is strongest among JavaScript and TypeScript users who want a small CLI rather than a hosted dependency bot. ### How it is used The common path is to run npx taze, optionally use -r for recursive monorepo scanning, and choose modes such as major, minor, patch, or stable to control how far versions are bumped. A taze.config.js file can store the same options available on the command line. ### Why package nerds care taze matters to package-manager culture because it is a package about packages: it automates dependency freshness while still respecting semver ranges and lockfile-era caution. It is especially interesting for monorepo maintainers who want a local, scriptable alternative to bot-driven upgrade workflows. ### Timeline - 2020: GitHub repository created. - 2022: Public GitHub release history includes the 0.8 series. - 2026: GitHub release metadata lists the 19.x series. ### Related projects - The README lists npm-check-updates and npm-check as inspirations or alternatives. ### Sources - - - - input.source_facts.package-manager ## Security Notes No matching local secret-handling manifest was found for taze. Nucleus package metadata is still published here so future coverage has a stable package URL. ## 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: taze.config.js ## Other Package-Manager Records - Nix - taze: normalized package name match | nixpkgs package indexes: pkgs/by-name/ta/taze/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/taze.yml](https://github.com/mxcl/pkgdb/blob/main/combined/taze.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph