Skip to content


Repository files navigation


The key idea of Reliquary is that it should be able to serve an interfance compatible with existing tools for a repository of packages. Additionally, it can function as a sort of caching proxy for upstream sources.

In a sense, it is comparible in desired function to "Binary Repository Manager" services, sometimes referred to as "Software Artifact Repositories."

For example, Python has a standard that is well known and used by tools like pip or buildout to fetch dependencies. Reliquary provides two implementations of this interface -- one that acts as a self hosted interface, and another that acts as a caching proxy to an upstream python package index.

Reliquary is not intended to be limited to just Python packages. CommonJS/NPM, APT, and any other standardized repository formats are all possible interfaces for Reliquary to implement.

Current Status

This project is very much in development, and will likely drastically change frequently.

Currently implemented are:

Planned Features for the near future:

  • configurable proxy upstream for python and commonjs end points
  • more work on authentication and authorization (more specific permissions, better mechanism for generating and storing basic auth keys, maybe private url scheme, maybe ldap integration)
  • debian repository compatible caching proxy
  • a mechanism for requesting a merged set of indices within a channel

Features that may be considered based on feasibility include a YUM and RubyGems interface. Other interfaces may be possible with interest.


Serves packages in standardized formats







No releases published


No packages published