Installation via brew command throws error

[toduyemi]

Description

2018 MacbookPro Sequoia 15.4.1

When attempting to install repomix via homebrew, the following error is thrown =>

 brew install repomix
==> Downloading https://ghcr.io/v2/homebrew/core/repomix/manifests/0.3.7
Already downloaded: /Users/temi/Library/Caches/Homebrew/downloads/9d9f0fbb552fe93b7c6004d694d917135adeba80dff8e30f8465b4289cb2353f--repomix-0.3.7.bottle_manifest.json
==> Fetching dependencies for repomix: libuv, ca-certificates and openssl@3
==> Downloading https://ghcr.io/v2/homebrew/core/libuv/manifests/1.51.0
Already downloaded: /Users/temi/Library/Caches/Homebrew/downloads/25bd9f2f86d047011dc8ca247bea2e4e3e5a150e29648418d48dfca4c8c136ea--libuv-1.51.0.bottle_manifest.json
==> Fetching libuv
==> Downloading https://ghcr.io/v2/homebrew/core/libuv/blobs/sha256:fb199706c025af4c6160825de25f9220c8d571499c5dba71c4b93a3874ea7a03
Already downloaded: /Users/temi/Library/Caches/Homebrew/downloads/d53fecfc1f0449b8a29d78c7364f8effa7f77965da02e57b732ad70621f29112--libuv--1.51.0.sonoma.bottle.tar.gz
==> Downloading https://ghcr.io/v2/homebrew/core/ca-certificates/manifests/2025-05-20
Already downloaded: /Users/temi/Library/Caches/Homebrew/downloads/bc18acc15e0abddc102f828b57a29cfdbec1b6b002db37ad12bad9dbf0e9d12f--ca-certificates-2025-05-20.bottle_manifest.json
==> Fetching ca-certificates
==> Downloading https://ghcr.io/v2/homebrew/core/ca-certificates/blobs/sha256:dda1100e7f994081a593d6a5e422451bfa20037e29667ed2b79f011ffc9288a7
curl: (56) The requested URL returned error: 503    #           #            #                                                                                         

Error: repomix: Failed to download resource "ca-certificates"
Download failed: https://ghcr.io/v2/homebrew/core/ca-certificates/blobs/sha256:dda1100e7f994081a593d6a5e422451bfa20037e29667ed2b79f011ffc9288a7

Usage Context

None

Repomix Version

No response

Node.js Version

No response

[yamadashy]

Hi, @toduyemi !
Thanks for the report!

I'll test this on my machine later, but since we're getting a 503 error from GitHub's servers, this looks like a temporary GitHub issue.