# ivy mit Homebrew, apt, MacPorts, Nix, dnf, zypper installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für ivy in AI-Agent-Workflows.
## Installation
```sh
sudo av install brew:ivy
```
Weitere Installationsbefehle:
### macOS
- Homebrew (100%):
```sh
brew install ivy
```
Evidenz: local Homebrew formula metadata
- MacPorts (94%):
```sh
sudo port install ivy
```
Evidenz: MacPorts ports tree: math/ivy/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
### Linux
- Debian apt (92%):
```sh
sudo apt install ivy
```
Evidenz: Debian stable package indexes: ivy from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz
- Nix (92%):
```sh
nix profile install nixpkgs#ivy
```
Evidenz: nixpkgs package indexes: pkgs/by-name/iv/ivy/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- dnf (92%):
```sh
sudo dnf install apache-ivy
```
Evidenz: Fedora Rawhide package metadata: apache-ivy from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst
- zypper (92%):
```sh
sudo zypper install apache-ivy
```
Evidenz: openSUSE Tumbleweed package metadata: apache-ivy from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst
## Paketfakten
- **Paketschlüssel:** brew:ivy
- **Paketmanager:** Homebrew
- **Version:** 2.6.0
- **Quellzusammenfassung:** Agile dependency manager
- **Homepage:**
- **Zuletzt aktualisiert:** 2026-07-15T20:53:58Z
- **Generiert:** 2026-08-03T19:37:03+00:00
## Executables
- ivy (Alias)
## Installationsverhalten
- Bottle: nicht verfügbar
## Version und Aktualität
- Seite generiert: 2026-08-03
- Manager-Version: 2.6.0
## Projektgeschichte und Nutzung
Apache Ivy is a Java dependency manager associated with Apache Ant. It records, tracks, resolves, reports, and retrieves project dependencies while staying process-agnostic and configurable rather than imposing a full build lifecycle.
### Projektgeschichte
Ivy began outside Apache under Jayasoft; the Apache documentation still notes that the documentation was migrated from the old Jayasoft web site. The Apache Ivy home page records its October 2007 graduation as a subproject of Ant, followed by the 2.0.0 beta and release-candidate cycle.
The 2.0.0 release in January 2009 was the first non-beta Ivy release under Apache. The release notes highlight the move from Jayasoft Ivy to Apache Ivy, Java package renaming from fr.jayasoft to org.apache, the settings-file terminology change from configuration to settings, and a default resolver move toward Maven 2-compatible ibiblio repositories.
The 2.x line developed Ivy into a long-lived Ant companion. Apache's release history lists 2.1.0 in 2009, 2.2.0 in 2010, 2.3.0 in 2013, 2.4.0 in 2014, 2.5.0 in 2019, and maintenance releases in the 2.5 series.
### Adoptionsgeschichte
Ivy's adoption came from Java projects that wanted transitive dependency resolution without moving the whole build to Maven. Its tight Ant integration let build.xml users add dependency resolution, reports, publishing, and retrieval while preserving existing Ant build structure.
The input package metadata shows Ivy packaged across Homebrew, Debian/Ubuntu, Fedora, MacPorts, Nix, and openSUSE. That broad packaging reflects its role as a build tool dependency for legacy and maintained Java build systems.
### Wie es verwendet wird
Ivy projects usually declare dependencies in ivy.xml and customize repositories, resolvers, caches, namespaces, credentials, and other behavior through ivysettings.xml. It can run as Ant tasks or as a standalone application, with the cache and retrieval model separating dependency resolution from local artifact layout.
Ivy is most often compared with Maven dependency management: it can consume Maven-style metadata and repositories, but its package-nerd appeal is that it keeps dependency resolution independent from a prescribed project model.
### Warum Paket-Nerds sich dafür interessieren
Ivy matters historically because it represents a flexible, XML-configured answer to Java dependency hell during the Ant era. It is also a useful study in package-manager interoperability: Ivy files, Maven POMs, resolvers, repositories, caches, conflict managers, and generated reports are all explicit pieces of its model.
### Zeitleiste
- 2007: Ivy graduated as a subproject of Apache Ant.
- 2009: Apache Ivy 2.0.0 was released as the first non-beta Apache release.
- 2010: Apache Ivy 2.2.0 was made available.
- 2014: Apache Ivy 2.4.0 was made available.
- 2019: Apache Ivy 2.5.0 was made available.
- 2024: Apache Ivy 2.5.3 was made available.
### Related projects
- Related projects include Apache Ant, Apache Maven, IvyDE for Eclipse, Maven-compatible repositories, ibiblio/Maven Central-style resolvers, and Java build systems that consume artifact metadata.
### Quellen
-
-
-
-
-
## 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: ivysettings.xml
## Andere Paketmanager-Einträge
- Debian apt - ivy - 2.5.3-1: normalized package name match | Debian stable package indexes: ivy from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | agile dependency manager | https://ant.apache.org/ivy/
- Debian apt - ivy-doc - 2.5.3-1: normalized package name match | Debian stable package indexes: ivy-doc from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | agile dependency manager (documentation) | https://ant.apache.org/ivy/
- Nix - ivy: normalized package name match | nixpkgs package indexes: pkgs/by-name/iv/ivy/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Ubuntu apt - ivy - 2.5.2-1: normalized package name match | Ubuntu 24.04 LTS package indexes: ivy from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | agile dependency manager | https://ant.apache.org/ivy/
- Ubuntu apt - ivy-doc - 2.5.2-1: normalized package name match | Ubuntu 24.04 LTS package indexes: ivy-doc from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | agile dependency manager (documentation) | https://ant.apache.org/ivy/
- dnf - apache-ivy - 2.6.0-2.fc45: normalized package name match | Fedora Rawhide package metadata: apache-ivy from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | Java-based dependency manager | https://ant.apache.org/ivy
- zypper - apache-ivy - 2.6.0-1.2: normalized package name match | openSUSE Tumbleweed package metadata: apache-ivy from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Java-based dependency manager | https://ant.apache.org/ivy/
- MacPorts - ivy: normalized package name match | MacPorts ports tree: math/ivy/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
## Combined YAML source
View the package source record on GitHub. [combined/ivy.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ivy.yml)
## Quellen
- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph