robocorp-vault
robocorp-vault is a library that provides read and write access to the Vault in Robocorp Control Room, which can be used to store and retrieve secret values such as passwords.
Getting started
A secret consists of a name, an optional description, and a map of keys and values. For instance, one secret can be login credentials for a website, which includes both a username and a password:
from robocorp.tasks import task
from robocorp import vault
@task
def inspect_secret():
secret = vault.get_secret("login_credentials")
print("Secret name:", secret.name)
print("Secret description:", secret.description)
print("Secret keys:", secret.keys())
print("Secret value:", secret["username"])
Guides
Further user guides and tutorials can be found in Robocorp Docs.
API Reference
Explore our API for extensive documentation.
Changelog
A list of releases and corresponding changes can be found in the changelog.
3 maintainers
Metadata
3 maintainers
Release files for robocorp-vault 1.4.2
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 |
|---|---|---|---|---|
| robocorp_vault-1.4.2.tar.gz | 10.7 kB | With provenance | Details for robocorp_vault-1.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| robocorp_vault-1.4.2-py3-none-any.whl | Python 3 | none | any | Details for robocorp_vault-1.4.2-py3-none-any.whl |
Total release size: 23.6 kB
Release files / robocorp_vault-1.4.2.tar.gz
| Download URL | robocorp_vault-1.4.2.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21faa82319f0c80024439f5d902b8ef6ba8bf72cdc485df3e9eb07f147984618
|
|
BLAKE2b-256 checksum How to use checksums |
27070e4ab1334809f7f3e949d238d52175b07747579698bdd40fc9f623b0fac4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 18, 2026.
Transparency logRelease files / robocorp_vault-1.4.2-py3-none-any.whl
| Download URL | robocorp_vault-1.4.2-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
77995a494cdb4bfaebb79a952435e2f2f230e8d4273d8eaaa7d977183ccde8cf
|
|
BLAKE2b-256 checksum How to use checksums |
52c09d88c707e03dc55db3e3fa4fac27b4514a5766130223eb443f2cdcd7bf2f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 18, 2026.
Transparency logSecurity for robocorp-vault 1.4.2
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for robocorp_vault-1.4.2.tar.gz
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 Oct 18, 2026.
Transparency logA 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.
