Software source code objects---e.g., individual source code files, tarballs, commits, tagged releases, etc.---are stored in the Software Heritage (SWH) Archive in fully deduplicated form. That allows direct access to individual artifacts but require some preparation, usually in the form of collecting and assemblying multiple artifacts in a single bundle, when fast access to a set of related artifacts (e.g., the snapshot of a VCS repository, the archive corresponding to a Git commit, or a specific software release as a zip archive) is required.
The Software Heritage Vault is a cache of pre-built source code bundles which are assembled opportunistically retrieving objects from the Software Heritage Archive, can be accessed efficiently, and might be garbage collected after a long period of non use.
|Resolved||seirl||T67 prototype: git clone from SWH|
|Resolved||seirl||T508 prototype: git archive from SWH|
|Resolved||seirl||T530 Software Heritage Vault|
|Resolved||seirl||T531 Vault cookers|
|Resolved||zack||T565 embrace repository snapshot object in the data model (meta task)|
|Resolved||None||T566 specify serialization format for repository snapshot objects|
|Resolved||None||T567 adapt SQL storage for repository snapshot objects|
|Resolved||olasd||T830 Remove tables occurrence and occurrence_history|
|Resolved||anlambert||T949 swh-web: Display origin-visit's details using snapshots|
|Resolved||seirl||T532 Vault API|