Software Heritage - Vault
User-facing service that allows to retrieve parts of the archive as self-contained bundles (e.g., individual releases, entire repository snapshots, etc.) The creation of a bundle is called “cooking” a bundle.
Architecture
The vault is made of two main parts:
a stateful RPC server called the backend
Celery tasks, called cookers
Metadata
Release files for swh.vault 2.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| swh_vault-2.1.0.tar.gz | 71.5 kB | Without provenance | Details for swh_vault-2.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| swh_vault-2.1.0-py3-none-any.whl | Python 3 | none | any | Details for swh_vault-2.1.0-py3-none-any.whl |
Total release size: 149.8 kB
Release files / swh_vault-2.1.0.tar.gz
| Download URL | swh_vault-2.1.0.tar.gz |
|---|---|
| Size | 71.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a1d5b4636fb4c281b3f364eff87985a2b09f56df83baecd85082320c40e8b4d1
|
|
BLAKE2b-256 checksum How to use checksums |
5678d791316ff463273882672e7d8ecb6d2c5cd6004ee2c36660221e1d3f72f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.12
|
Release files / swh_vault-2.1.0-py3-none-any.whl
| Download URL | swh_vault-2.1.0-py3-none-any.whl |
|---|---|
| Size | 78.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b4f7b9cd712d0ee652e472d700fa891141b58235f7d621968985d13dc0b4e0f4
|
|
BLAKE2b-256 checksum How to use checksums |
db14bca735388d6fdf723f8cab249838c7b6a78a3e229f2875ec47c78b546869
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.12
|
Security for swh.vault 2.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.