Skip to main content

SDK for interacting with Nillion’s Private Storage solutions.

PyPI version and link. Read the Docs documentation status. GitHub Actions status. Coveralls test coverage summary.

Installation and Usage

You can install the package using pip:

pip install secretvaults

The library can be imported in the usual ways:

import secretvaults
from secretvaults import *

Examples and Usage Documentation

Please see the examples directory for examples and documentation.

Development

All installation and development dependencies are fully specified in pyproject.toml. The project.optional-dependencies object is used to specify optional requirements for various development tasks. This makes it possible to specify additional options (such as docs, lint, and so on) when performing installation using pip:

python -m pip install ".[docs,lint]"

Documentation

The documentation can be generated automatically from the source files using Sphinx:

python -m pip install ".[docs]"
cd docs
sphinx-apidoc -f -E --templatedir=_templates -o _source ../src && make html

Testing and Conventions

All unit tests are executed and their coverage is measured when using pytest (see the pyproject.toml file for configuration details):

python -m pip install ".[test]"
python -m pytest test

Style conventions are enforced using Pylint:

python -m pip install ".[lint]"
python -m pylint src/secretvaults

Contributions

In order to contribute to the source code, open an issue or submit a pull request on the GitHub page for this library.

Versioning

The version number format for this library and the changes to the library associated with version number increments conform with Semantic Versioning 2.0.0.

Publishing

This library can be published as a package on PyPI via the GitHub Actions workflow found in .github/workflows/build-publish-sign-release.yml that follows the recommendations found in the Python Packaging User Guide.

Ensure that any links in this README document to the Read the Docs documentation of this package (or its dependencies) have appropriate version numbers. Also ensure that the Read the Docs project for this library has an automation rule that activates and sets as the default all tagged versions.

Metadata

Release files for secretvaults 0.3.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for secretvaults 0.3.2
File Size Uploaded
secretvaults-0.3.2.tar.gz 30.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for secretvaults 0.3.2
File Interpreter ABI Platform
secretvaults-0.3.2-py3-none-any.whl Python 3 none any Details

Total release size: 67.4 kB

Release files / secretvaults-0.3.2.tar.gz

Download URL secretvaults-0.3.2.tar.gz
Size 30.0 kB
Tags Source
SHA-256 checksum
How to use checksums
660dd9c1bda1c1d0395b4ed16ff6cf0fc6d6587ad0a9bd7061640d05f4644f41
BLAKE2b-256 checksum
How to use checksums
fb4331433116c5795679b6f5b92129732e2209cf421628dcff9bfec527b0e6c2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 4, 2025.

Transparency log

Release files / secretvaults-0.3.2-py3-none-any.whl

Download URL secretvaults-0.3.2-py3-none-any.whl
Size 37.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
65a3158b287ea106d7369723b9a53bcb5c6786974c74634bce71b1d71fba33f9
BLAKE2b-256 checksum
How to use checksums
d1dfa3e34005625cad877e93c62050b8715caa451fb254ea9f020e9afc5f5f60
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 4, 2025.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page