macOS
brew install grunt-clilocal Homebrew formula metadata
brew
JavaScript Task Runner. Version 1.5.0 via Homebrew; verified from local package data.
install
brew install grunt-clilocal Homebrew formula metadata
nix profile install nixpkgs#grunt-clinixpkgs package indexes · pkgs/by-name/gr/grunt-cli/package.nix · source: api.github.com
sudo pacman -S grunt-cliArch Linux sync databases · grunt-cli · source: geo.mirror.pkgbuild.com
sudo apt install gruntDebian stable package indexes · grunt · source: deb.debian.org
winget install --id Grunt.Grunt -eWindows Package Manager source index · Grunt.Grunt · source: cdn.winget.microsoft.com
overview
JavaScript Task Runner
history
grunt-cli is the small command-line launcher for Grunt, the JavaScript task runner. Its importance is not that it contains the build system itself, but that it standardizes the global or local `grunt` command while delegating execution to the Grunt version installed beside a project Gruntfile.
The Grunt ecosystem began with the core grunt repository in September 2011 and the dedicated grunt-cli repository in November 2012. The CLI split reflects a Node.js packaging lesson: the executable can live globally while the task runner and plugins stay pinned in each project.
Grunt documentation for the 0.4 era explicitly tells users that installing grunt-cli does not install the Grunt task runner. Instead, each `grunt` invocation searches through Node's require system for a local Grunt installation, reads the project Gruntfile, and runs requested tasks. The grunt-cli npm package was created in November 2012, matching the repository's early public history.
grunt-cli was widely adopted with Grunt during the early Node.js build-tool era, when JavaScript projects needed repeatable commands for minification, linting, concatenation, tests, and release chores. Its global-install pattern let developers type `grunt` in many projects while allowing each project to control its own Grunt and plugin versions.
As npm scripts and later bundlers became more common, grunt-cli's role narrowed but remained historically important: it is the launcher that made Grunt's project-local dependency model ergonomic across shells, editors, CI systems, and package managers.
Typical use is `npm install -g grunt-cli` to place `grunt` on PATH, followed by project-local installation of `grunt` and plugins as development dependencies. Running `grunt` from a project directory locates the nearest Gruntfile, loads project tasks, and executes the named or default task. The CLI also exposes options for help, base path, alternate Gruntfile, task directories, npm-installed plugins, dry-run behavior, verbosity, version output, and shell completion.
grunt-cli is package-manager lore because it encodes the global-binary/local-library compromise that became common in Node tooling. It gives Homebrew, npm, Debian, Arch, Nix, Ubuntu, and Windows package entries a simple executable to ship, while project correctness still depends on `package.json` and the local `node_modules` graph.
For maintainers, grunt-cli is also a reminder that a package named like a tool can be only a shim. Installing it gives users the command, not necessarily the task runner semantics until a project supplies a Gruntfile and dependencies.
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.
./Gruntfile.js./Gruntfile.coffeeexecutables
| Command | Kind | Exposure | Note |
|---|---|---|---|
grunt | cli | global executable |
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:grunt-cli |
|---|---|
| Version | 1.5.0 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/grunt-cli |
| Homepage | https://gruntjs.com/ |
| Repository | https://github.com/gruntjs/grunt-cli |
| Upstream docs | https://github.com/gruntjs/grunt-cli#readme |
| License | MIT |
| Source archive | https://registry.npmjs.org/grunt-cli/-/grunt-cli-1.5.0.tgz |
| Dependencies | node |
| Bottle | available (on all) |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | grunt-cli |
| Version Scheme | 0 |
| Revision | 0 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
grunt-cli
nix profile install nixpkgs#grunt-cligrunt-cli 1.5.0-1
The grunt command line interface.
sudo pacman -S grunt-cligrunt 1.6.1-1
JavaScript task runner/build system/maintainer tool
sudo apt install gruntgrunt 1.6.1-1
JavaScript task runner/build system/maintainer tool
sudo apt install gruntGrunt.Grunt
winget install --id Grunt.Grunt -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.