Software Heritage - Development Documentation¶
Software Architecture ← go there to have a glimpse on the Software Heritage software architecture
Here is brief overview of the most relevant software components in the Software Heritage stack. Each component name is linked to the development documentation of the corresponding Python module.
low-level utilities and helpers used by almost all other modules in the stack
public datasets and periodic data dumps of the archive released by Software Heritage
push-based deposit of software artifacts to the archive
developer documentation (used to generate this doc you are reading)
Fast, compressed, in-memory representation of the archive, with tooling to generate and query it.
tools and workers used to crawl the content of the archive and extract derived information from any artifact stored in it
persistent logger of changes to the archive, with publish-subscribe support
collection of listers for all sorts of source code hosting and distribution places (forges, distributions, package managers, etc.)
low-level loading utilities and helpers used by all other loaders
loader for Git repositories
loader for Mercurial repositories
loader for Subversion repositories
implementation of the Data model to archive source code artifacts
content-addressable object storage
task manager for asynchronous/delayed tasks, used for recurrent (e.g., listing a forge, loading new stuff from a Git repository) and one-off activities (e.g., loading a specific version of a source package)
abstraction layer over the archive, allowing to access all stored source code artifacts as well as their metadata
implementation of the vault service, allowing to retrieve parts of the archive as self-contained bundles (e.g., individual releases, entire repository snapshots, etc.)
Web application(s) to browse the archive, for both interactive (HTML UI) and mechanized (REST API) use
The dependency relationships among the various modules are depicted below.