PHPackages                             jnettik/terminus-mass-run - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. jnettik/terminus-mass-run

ActiveTerminus-plugin

jnettik/terminus-mass-run
=========================

Run Terminus commands on multiple Pantheon sites.

11023PHP

Since Feb 27Pushed 7y ago1 watchersCompare

[ Source](https://github.com/jnettik/terminus-mass-run)[ Packagist](https://packagist.org/packages/jnettik/terminus-mass-run)[ RSS](/packages/jnettik-terminus-mass-run/feed)WikiDiscussions master Synced yesterday

READMEChangelogDependenciesVersions (1)Used By (0)

Terminus Mass Run
=================

[](#terminus-mass-run)

Terminus Mass Run takes a piped list of Pantheon sites runs a Terminus command on them in bulk. This takes the idea used in [Terminus Mass Update](https://github.com/pantheon-systems/terminus-mass-update) and expands on it for various terminus commands. Currently supported commands are:

- `terminus remote:drush`
- `terminus backup:create`
- `terminus env:deploy`
- `terminus connection:set`
- `terminus site:upstream:clear-cache`

Terminus provides several ways of getting a list of sites, the simplest being `terminus site:list --format=list`. The `--format=list` flat gets a list of site IDs that can be passed into Terminus Mass Run commands. For example, say you need to rebuild the cache on all production sites you have access too. Run:

```
$ terminus site:list --format=list | terminus remote:mass:drush -- cr

```

###  Health Score

22

—

LowBetter than 22% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity13

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity38

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/4a72adf1727257f258b76df137fd48e98d4a74db1fdde9148ebc92b240a97952?d=identicon)[jnettik](/maintainers/jnettik)

---

Top Contributors

[![jnettik](https://avatars.githubusercontent.com/u/720018?v=4)](https://github.com/jnettik "jnettik (19 commits)")

### Embed Badge

![Health badge](/badges/jnettik-terminus-mass-run/health.svg)

```
[![Health](https://phpackages.com/badges/jnettik-terminus-mass-run/health.svg)](https://phpackages.com/packages/jnettik-terminus-mass-run)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)