macOS
brew install ivylocal Homebrew formula metadata
sudo port install ivyMacPorts ports tree · math/ivy/Portfile · source: api.github.com
brew
Agile dependency manager. Version 2.5.3 via Homebrew; verified from local package data.
install
brew install ivylocal Homebrew formula metadata
sudo port install ivyMacPorts ports tree · math/ivy/Portfile · source: api.github.com
sudo apt install ivyDebian stable package indexes · ivy · source: deb.debian.org
sudo dnf install apache-ivyFedora Rawhide package metadata · apache-ivy · source: dl.fedoraproject.org
nix profile install nixpkgs#ivynixpkgs package indexes · pkgs/by-name/iv/ivy/package.nix · source: api.github.com
sudo zypper install apache-ivyopenSUSE Tumbleweed package metadata · apache-ivy · source: download.opensuse.org
overview
Agile dependency manager
history
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.
security posture
infrastructure mutation or orchestration signal.
orange risk · medium confidence · infrastructure
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
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
| Command | Kind | Exposure | Note |
|---|---|---|---|
ivy | cli | global executable |
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
install metadata
| Package key | brew:ivy |
|---|---|
| Version | 2.5.3 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/ivy |
| Homepage | https://ant.apache.org/ivy/ |
| Repository | https://gitbox.apache.org/repos/asf/ant-ivy.git |
| Upstream docs | https://ant.apache.org/ivy |
| License | Apache-2.0 |
| Source archive | https://www.apache.org/dyn/closer.lua?path=ant/ivy/2.5.3/apache-ivy-2.5.3-bin.tar.gz |
| Dependencies | openjdk |
| Bottle | available (on all) |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | ivy |
| Version Scheme | 0 |
| Revision | 0 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
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.5.2-6.fc42
Java-based dependency manager
sudo dnf install apache-ivyapache-ivy 2.5.3-2.3
Java-based dependency manager
sudo zypper install apache-ivyivy
sudo port install ivysource trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.