macOS
brew install ivylocal Homebrew formula metadata
sudo port install ivyMacPorts ports tree · math/ivy/Portfile · Quelle: api.github.com
brew / Rang 6280
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für ivy in AI-Agent-Workflows.
Installation
brew install ivylocal Homebrew formula metadata
sudo port install ivyMacPorts ports tree · math/ivy/Portfile · Quelle: api.github.com
sudo apt install ivyDebian stable package indexes · ivy · Quelle: deb.debian.org
nix profile install nixpkgs#ivynixpkgs package indexes · pkgs/by-name/iv/ivy/package.nix · Quelle: api.github.com
sudo dnf install apache-ivyFedora Rawhide package metadata · apache-ivy · Quelle: dl.fedoraproject.org
sudo zypper install apache-ivyopenSUSE Tumbleweed package metadata · apache-ivy · Quelle: download.opensuse.org
Überblick
Agile dependency manager
Verlauf
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.
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.
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.
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.
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.
Sicherheitslage
infrastructure mutation or orchestration signal.
orange Risiko · mittel Konfidenz · infrastructure
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
local files
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.
Config paths the tool may read or write during local use.
ivysettings.xmlExecutables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
ivy | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
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.
Installationsmetadaten
| Paketschlüssel | brew:ivy |
|---|---|
| Version | 2.6.0 |
| Paketmanager | Homebrew |
| Homepage | https://ant.apache.org/ivy/ |
| Zuletzt aktualisiert | 2026-07-15T20:53:58Z |
| Pulse | updated |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
Source-Datenbank-Treffer
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
ivy 2.5.3-1
agile dependency manager
sudo apt install ivyivy-doc 2.5.3-1
agile dependency manager (documentation)
sudo apt install ivy-docivy
nix profile install nixpkgs#ivyivy 2.5.2-1
agile dependency manager
sudo apt install ivyivy-doc 2.5.2-1
agile dependency manager (documentation)
sudo apt install ivy-docapache-ivy 2.6.0-2.fc45
Java-based dependency manager
sudo dnf install apache-ivyapache-ivy 2.6.0-1.2
Java-based dependency manager
sudo zypper install apache-ivyivy
sudo port install ivyQuellspur
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
View the package source record on GitHub.