Automic VaultAutomic Vault

brew

bluepill mit Homebrew, winget installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für bluepill in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install bluepill

local Homebrew formula metadata

Windows

Windows Package Managerverifiziert · 92%
winget install --id Ukhirani.Bp -e

Windows Package Manager source index · Ukhirani.Bp · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

Testing tool for iOS that runs UI tests using multiple simulators

Befehle und Aliase

  • bluepill
  • bp

Verlauf

Projektgeschichte und Nutzung

Bluepill is an iOS test runner created at LinkedIn to run large XCTest and UI-test suites across multiple simulators on one Mac. It became a recognizable package for iOS CI teams because it attacked the slow, flaky simulator-test problem before Apple's own parallel-test story was mature.

Projektgeschichte

LinkedIn open-sourced Bluepill in January 2017 after building it to run its large iOS test suite in a reasonable amount of time. The README describes its core features: parallel simulator execution, automatic test grouping, headless mode, junit reports, retry behavior, and simulator crash or hang recovery.

The project was originally published under LinkedIn's GitHub organization and later lives under MobileNativeFoundation. Its tags show a long 5.x release line, and the README tracks supported Xcode versions with branches for older Xcode releases.

Adoptionsgeschichte

Bluepill found adoption among iOS teams that needed faster CI feedback without rewriting tests. The README explicitly documents Homebrew installation, release binaries, Fastlane plugin integrations, and a Bitrise build/test step, showing that usage spread through common mobile CI packaging channels.

The surrounding ecosystem included Redpill and other Fastlane plugins, plus Bitrise support, which let teams wire Bluepill into existing build pipelines rather than treating it as a standalone experiment.

Wie es verwendet wird

A typical workflow builds an app and test bundle with xcodebuild build-for-testing, then invokes bluepill with the generated .xctestrun file and an output directory. The tool can also read a JSON configuration file via -c/--config, but the README documents this as a user-supplied file rather than a fixed config path.

Operationally, Bluepill matters because it packs tests into simulator groups, controls retry behavior, collects junit output, and can run headless to reduce resource use on CI machines.

Warum Paket-Nerds sich dafür interessieren

Bluepill is significant because it packages a hard local-platform problem: reproducible iOS simulator parallelism. For package nerds, it is a case study in a CLI wrapping Xcode artifacts, Simulator behavior, junit reporting, and CI integration into something installable with Homebrew.

It also marks a particular era of iOS infrastructure, when teams combined xctool, FBSimulatorControl ideas, Fastlane plugins, and custom runners to make Apple-platform testing scale in CI.

Zeitleiste

  • 2017: LinkedIn open-sourced Bluepill and published early v0.x tags.
  • 2017: README credits inspiration from parallel_ios_tests, Facebook xctool, and FBSimulatorControl.
  • 2017-2018: Fastlane and Bitrise integrations appeared around the project ecosystem.
  • 2024: Official repository metadata and tags show continued releases through the 5.x line, including Xcode 15.1-era work.

Related projects

  • parallel_ios_tests inspired the project.
  • Facebook xctool and FBSimulatorControl are credited by the README as inspirations.
  • Fastlane plugins such as Redpill, fastlane-plugin-bluepill, Bluepillar, and XBluepill integrated Bluepill into mobile release workflows.
  • Bitrise's Bluepill Build/Test for iOS step connected it to hosted CI.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 8 Plattformziele verfügbar.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
bluepillcliglobales Executable
bpcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version5.13.0
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/MobileNativeFoundation/bluepill

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:bluepill
Version5.13.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/bluepill
Homepagehttps://github.com/MobileNativeFoundation/bluepill
Repositoryhttps://github.com/MobileNativeFoundation/bluepill
Upstream-Dokumentationhttps://github.com/MobileNativeFoundation/bluepill#readme
LizenzBSD-2-Clause
Quellarchivhttps://github.com/MobileNativeFoundation/bluepill.git
Bottleverfügbar (auf arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, monterey, sonoma, ventura)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namebluepill
Version Scheme0
Revision0
Head VersionHEAD
Requirements
  • macos
  • xcode
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

winget92%

Ukhirani.Bp

winget install --id Ukhirani.Bp -e
  • installed executable or alias match
  • Abgeglichen nach: Bp
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Ukhirani.Bp from https://cdn.winget.microsoft.com/cache/source.msix

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment