pkg.soopen package index

brew / Rang 1179

carthage mit Homebrew, MacPorts installieren

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

InstallationsbefehlSicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install carthage

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install carthage

MacPorts ports tree · devel/carthage/Portfile · Quelle: api.github.com

Überblick

Paketzusammenfassung

Decentralized dependency manager for Cocoa

Befehle und Aliase

  • carthage

Verlauf

Projektgeschichte und Nutzung

Carthage is a decentralized dependency manager for Cocoa. Its README says it builds dependencies and provides binary frameworks while leaving project structure and build settings under the developer's control.

Projektgeschichte

The public repository was created in 2014, during the period when Swift and modern Cocoa dependency management were taking shape. Carthage's official pitch was simplicity and decentralization: dependencies are declared in a Cartfile, resolved to exact versions in Cartfile.resolved, and built or downloaded without automatically editing the Xcode project.

Adoptionsgeschichte

Carthage became a major alternative to CocoaPods for iOS and macOS projects that preferred explicit framework integration. Its documentation emphasizes manual Xcode integration, shared schemes, tagged releases, binary framework archives, and reproducible bootstrap through committed Cartfile.resolved files.

Wie es verwendet wird

A typical project creates a Cartfile next to its .xcodeproj or .xcworkspace, runs carthage update, then adds built frameworks or XCFrameworks from Carthage/Build into Xcode. Carthage can also checkout dependencies into Carthage/Checkouts, use Git submodules, cache builds, and authenticate binary framework downloads through ~/.netrc when --use-netrc is set.

Warum Paket-Nerds sich dafür interessieren

Carthage is one of the canonical package-manager stories in Apple development: it rejects project mutation as a feature, relies on Git tags and semantic versions, and treats dependency builds as visible artifacts. For package-manager catalogs, it is a historically important Cocoa tool because it captures a distinct design point from CocoaPods and Swift Package Manager.

Zeitleiste

  • 2014: Public GitHub repository created.
  • 2021: README says version 0.37.0 encouraged XCFrameworks and required them for Apple Silicon Macs.
  • 2020s: Documentation describes Cartfile, Cartfile.private, Cartfile.resolved, Carthage/Build, Carthage/Checkouts, and the shared cache under ~/Library/Caches/org.carthage.CarthageKit.

Related projects

  • Official documentation compares Carthage's approach with CocoaPods.
  • Carthage operates in the Cocoa, Xcode, Swift, iOS, macOS, tvOS, and watchOS ecosystem.
  • Its artifacts and binary-project-specification docs connect it to GitHub releases and HTTPS-hosted framework archives.

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:dependency manager

Installationsverhalten

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

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.

local files

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

Config paths the tool may read or write during local use.

Unix
./Cartfile./Cartfile.private./Cartfile.resolved

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.netrc

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
carthageExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

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-08-03
Manager-Version0.40.0
Manager aktualisiert
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:carthage
Version0.40.0
PaketmanagerHomebrew
Homepagehttps://github.com/Carthage/Carthage
Repositoryhttps://github.com/Carthage/Carthage
Bottlenicht erfasst
Dienstkeiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

MacPorts95%

carthage

sudo port install carthage
  • normalized package name match
  • Abgeglichen nach: Carthage
MacPorts ports tree · api.github.com · MacPorts ports tree: devel/carthage/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

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
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation