# Install juise with Homebrew

JUNOS user interface scripting environment. Version 3.0.0 via Homebrew; verified 2026-07-03.

## Install

```sh
sudo av install brew:juise
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install juise
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:juise
- **Package manager:** Homebrew
- **Version:** 3.0.0
- **Source summary:** JUNOS user interface scripting environment
- **Homepage:** <https://github.com/Juniper/juise/wiki>
- **Repository:** <https://github.com/Juniper/juise>
- **Last updated:** 2026-07-03T16:47:36-04:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- juise (alias)
- juise-config (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 3.0.0
## Project history and usage

juise is Juniper's JUNOS User Interface Scripting Environment, a desktop-side environment for writing, testing, debugging, and running Junos-oriented SLAX scripts outside the normal Junos device environment.

### Project history

The official repository and manual describe JUISE as tooling for SLAX scripts that interact with Junos XML data through Junos-specific extension functions. The repository tag history includes a 0.5.1 tag from July 2013 and a later 0.6.0 line, reflecting a specialized toolchain rather than a broad application platform.

### Adoption history

Adoption evidence is narrow and mostly tied to Juniper network automation users. Homebrew packaging made it installable on macOS for engineers who wanted an off-box Junos scripting workflow.

### How it is used

Network engineers use juise to develop and debug op, commit, and related Junos scripts without copying each iteration to a router or switch. It is most relevant in environments that still rely on SLAX and Junos XML scripting.

### Why package nerds care

juise is interesting because it packages vendor-specific network automation tooling as a Unix CLI. It captures an older, XML-and-SLAX-centered automation era before Python, NETCONF libraries, and controller-driven workflows became more common.

### Timeline

- 2013: The public repository tag history includes the 0.5.1 tag.
- 2015: Juniper community material described SLAX as a language for Junos commit, op, and event scripts.
- 2016: The repository tag history includes the 0.6.0 tag.

### Related projects

- libslax is the related SLAX processing library used in the same Junos scripting ecosystem.
- Juniper PyEZ is a later Python-oriented Junos automation project.
- junoscriptorium is Juniper's repository of Junos script examples.

### Sources

- <https://formulae.brew.sh/formula/juise>
- <https://github.com/Juniper/juise>
- <https://github.com/Juniper/juise/tags>
- <https://github.com/Juniper/junoscriptorium>
- <https://github.com/Juniper/py-junos-eznc>
- <https://juniper.github.io/juise/juise-manual.html>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Combined YAML source

View the package source record on GitHub. [combined/juise.yml](https://github.com/mxcl/pkgdb/blob/main/combined/juise.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph