# Install spago with Homebrew

PureScript package manager and build tool. Version 1.0.4 via Homebrew; verified from local package data.

## Install

```sh
sudo av install brew:spago
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install spago
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:spago
- **Package manager:** Homebrew
- **Version:** 1.0.4
- **Source summary:** PureScript package manager and build tool
- **Homepage:** <https://github.com/purescript/spago>
- **Repository:** <https://github.com/purescript/spago>
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- spago (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Spago is the PureScript package manager and build tool. It sits in the small-language tooling tradition where a single CLI handles project initialization, dependency resolution, builds, tests, REPL workflows, and publishing.

### Project history

The public repository was created in 2018 under the PureScript organization. The current README notes a rewrite of Spago in PureScript and directs users looking for versions up to 0.21.x to the legacy Haskell codebase.

### Adoption history

Spago became important in PureScript because it wrapped older ecosystem tools and ideas into one workflow. Its README names Cargo, Stack, psc-package, Pulp, and Bazel as inspirations, and its migration notes explicitly cover moving from `bower` and from the older `spago.dhall` configuration to `spago.yaml`.

### How it is used

A typical session is `spago init`, edit `spago.yaml`, then use commands such as `spago run`, `spago build`, `spago test`, `spago repl`, and package-set queries. The README recommends installing with npm across Windows, Linux, and macOS, while Homebrew packages it for users who prefer system package-manager workflows.

### Why package nerds care

Spago is interesting to package-tool people because it exposes PureScript's package-set model, registry migration, lock files, monorepo support, and JavaScript output workflow in one CLI. It shows how a niche language ecosystem can converge on Cargo-like ergonomics without simply copying npm.

### Timeline

- 2018: Public GitHub repository created.
- 2020s: Current README documents the PureScript rewrite and legacy Haskell-codebase cutoff at versions up to 0.21.x.
- 2020s: `spago.yaml` replaces the older Dhall-based configuration path for the new codebase.

### Related projects

- Related PureScript tooling includes the PureScript compiler, psc-package, Pulp, PureScript package sets, the PureScript registry, and spago-legacy.

### Sources

- <https://api.github.com/repos/purescript/spago>
- <https://github.com/purescript/spago>
- <https://raw.githubusercontent.com/purescript/spago/master/README.md>
- input.source_facts.package-manager


## Security Notes

generalized runtime or code generation signal. infrastructure mutation or orchestration signal.

- **Geiger risk:** orange / medium
- generalized runtime or code generation signal
- infrastructure mutation or orchestration 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: spago.yaml

## Combined YAML source

View the package source record on GitHub. [combined/spago.yml](https://github.com/mxcl/pkgdb/blob/main/combined/spago.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