# swift-outdated mit Homebrew installieren

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

## Installation

```sh
sudo av install brew:swift-outdated
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install swift-outdated
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:swift-outdated
- **Paketmanager:** Homebrew
- **Version:** 0.15.3
- **Quellzusammenfassung:** Check for outdated Swift package manager dependencies
- **Homepage:** <https://github.com/kiliankoe/swift-outdated>
- **Repository:** <https://github.com/kiliankoe/swift-outdated>
- **Zuletzt aktualisiert:** 2026-07-03T14:36:10Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- swift-outdated (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.15.3
## Projektgeschichte und Nutzung

swift-outdated is a Swift command-line tool for showing when Swift package dependencies have newer versions available outside the versions currently resolved by Swift Package Manager, Tuist, or Xcode.

### Projektgeschichte

The public GitHub repository was created in 2020. Its README describes the tool as a Swift subcommand inspired by cargo-outdated, adapting the familiar package-manager workflow of checking remote tags for newer dependency releases to Swift projects.

### Adoptionsgeschichte

The project is packaged for Homebrew and Mint, which puts it in the normal install paths used by Swift command-line developers. Homebrew lists bottles for macOS and Linux, while the README documents invocation as `swift outdated`, matching Swift's subcommand convention.

### Wie es verwendet wird

Typical usage is running `swift outdated` in a project to compare resolved package versions against upstream tags. The README documents direct versus transitive dependency reporting, package-registry dependencies, branch and revision pins, fork-upstream mapping, Xcode project support, and optional security checks through OSV and OpenSSF Scorecard.

### Warum Paket-Nerds sich dafür interessieren

The tool fills a gap package-manager users notice quickly: `swift package update` respects declared requirements, so it can leave major releases invisible. swift-outdated makes Swift dependency drift visible in the same culture as `npm outdated` or `cargo outdated`, including the tricky cases of forks, registry dependencies, and Xcode-managed packages.

### Zeitleiste

- 2020: Public GitHub repository created.
- Current docs: Installed by Homebrew or Mint and invoked as `swift outdated`.
- Current docs: Supports SwiftPM, Tuist, plain Xcode projects, package registries, fork mappings, branch and revision pins, and security checks.

### Related projects

- The README names cargo-outdated as an inspiration and documents SwiftPM, Tuist, Xcode package references, OSV, and OpenSSF Scorecard as part of the supported workflow.

### Quellen

- <https://api.github.com/repos/kiliankoe/swift-outdated>
- <https://formulae.brew.sh/api/formula/swift-outdated.json>
- <https://github.com/kiliankoe/swift-outdated#readme>
- source_facts.description


## Sicherheitshinweise

infrastructure mutation or orchestration signal.

- **Geiger-Risiko:** orange / mittel
- 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: .swift-outdated.yml

## Combined YAML source

View the package source record on GitHub. [combined/swift-outdated.yml](https://github.com/mxcl/pkgdb/blob/main/combined/swift-outdated.yml)


## Quellen

- 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