Skip to main content

Object Storage Client

One URL-based API for AWS S3, Google Cloud Storage, Azure Blob Storage, HTTP(S) and the local filesystem, as a Rust library, Python bindings and the osc command-line tool. The scheme of each URL picks the backend, so a single client can copy and move objects between providers, stream large objects in bounded memory (see Behaviour for the limits) and generate pre-signed URLs. Optional client-side encryption keeps object contents hidden from the storage provider.

  • One API for every backend, including cross-provider copy and move.
  • Streaming uploads and downloads, with multipart uploads for large objects.
  • Listing of a prefix or a whole bucket (flat and recursive), existence checks and bucket creation.
  • Pre-signed URLs for S3, GCS and Azure. An s3:// URL signed with temporary credentials stops working when that session ends, whatever expiry was requested.
  • AWS profiles and SSO for s3://: osc --profile NAME, ObjectStorageClient(profile="NAME") in Python and with_s3_profile in Rust; see AWS profiles and SSO.
  • Client-side encryption (Cargo feature encryption, on by default) with self-reloading keyrings and key rotation.
URL Backend
s3://bucket/key AWS S3 and S3-compatible stores (Garage, SeaweedFS, …)
gs://bucket/key, gcs://bucket/key Google Cloud Storage
az://, wasb(s)://, abfs(s):// + container/key Azure Blob Storage
http://host/path, https://host/path HTTP/HTTPS
file:///abs/path, /abs/path, ~/path, relative/path Local filesystem

For the cloud schemes the host is the bucket or container and the path is the object key. A bucket-root URL such as s3://bucket addresses the bucket itself: list it, create it or check that it exists. Credentials come from environment variables or, for s3://, from a named AWS profile; see Configuration.

Rust

The crate is published to the Bixority Codeberg crate registry:

export CARGO_REGISTRIES_BIXORITY_INDEX="sparse+https://codeberg.org/api/packages/bixority/cargo/"
[dependencies]
object-storage-client = { version = "0.4", registry = "bixority" }
# or: object-storage-client = { git = "https://codeberg.org/bixority/object-storage-client" }
tokio = { version = "1", features = ["full"] }

The encryption and cli features are on by default. A library that does not need the CLI can drop clap and tokio-util:

object-storage-client = { version = "0.4", registry = "bixority", default-features = false, features = ["encryption"] }
use object_storage_client::{ObjectStorageClient, SignMethod, SignOptions};
use std::time::Duration;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let client = ObjectStorageClient::new();

    // Create a bucket (S3/GCS/Azure, or a directory for file:// URLs); success if it is already yours
    client.create_bucket("s3://my-bucket").await?;

    // Upload data to S3
    client.put("s3://my-bucket/hello.txt", &b"Hello from Rust!"[..]).await?;

    // Download it back
    let retrieved = client.get("s3://my-bucket/hello.txt").await?;
    println!("Retrieved: {}", String::from_utf8_lossy(&retrieved));

    // List the whole bucket from a bucket-root URL (flat, recursive: every key
    // is returned). Pass a prefix such as "s3://my-bucket/logs/" to narrow it.
    let keys = client.list("s3://my-bucket").await?;
    println!("Bucket keys: {keys:?}");

    // Existence checks (missing -> Ok(false), never an error)
    if client.bucket_exists("s3://my-bucket").await? {
        println!("my-bucket is present");
    }
    if client.exists("s3://my-bucket/hello.txt").await? {
        println!("hello.txt is present");
    }

    // --- Move data across providers with one client ---

    // Copy S3 -> Google Cloud Storage (source is left in place)
    client
        .copy("s3://my-bucket/hello.txt", "gs://my-gcs-bucket/hello.txt")
        .await?;

    // Move GCS -> Azure Blob Storage (source is deleted afterwards)
    client
        .move_object("gs://my-gcs-bucket/hello.txt", "az://my-container/hello.txt")
        .await?;

    // Copy Azure -> local disk for a working copy
    client
        .copy("az://my-container/hello.txt", "file:///tmp/hello_local.txt")
        .await?;

    // --- Pre-signed URLs: time-limited, credential-free access (S3/GCS/Azure) ---

    // Pre-signed download (GET) link, valid for one hour
    let download_url = client
        .get_pre_signed_url(
            "s3://my-bucket/hello.txt",
            SignMethod::Get,
            Duration::from_secs(3600),
            &SignOptions::default(),
        )
        .await?;
    println!("Share this download link: {download_url}");

    // Pre-signed upload (PUT) link binding the exact size and type the client
    // must send (S3 only); the store rejects mismatched uploads up front.
    let upload_url = client
        .get_pre_signed_url(
            "s3://my-bucket/upload.bin",
            SignMethod::Put,
            Duration::from_secs(900),
            &SignOptions {
                content_length: Some(1_048_576),
                content_type: Some("application/octet-stream".to_string()),
            },
        )
        .await?;
    println!("Upload directly to: {upload_url}");

    Ok(())
}

With encryption, the same calls on an encrypting view:

use object_storage_client::encryption::{EncryptionConfig, Keyring};
use object_storage_client::ObjectStorageClient;
use std::sync::Arc;

let keyring = Arc::new(Keyring::from_file("/var/run/secrets/osc/keyring")?); // reloads itself
let secure = ObjectStorageClient::new().with_encryption(EncryptionConfig::new(keyring.clone()));

secure.put("s3://my-bucket/payroll.csv", &b"id,salary"[..]).await?; // only ciphertext is stored
let csv = secure.get("s3://my-bucket/payroll.csv").await?;          // authenticated before it is returned
let health = keyring.status(); // active key, key ages, last reload error

Python

The package is published on PyPI and needs Python 3.13+:

pip install object-storage-client

Wheels exist for GIL CPython 3.13-3.15 on manylinux x86_64/aarch64, macOS arm64 and Windows x86_64; other platforms build the sdist and need Rust 1.99 or newer. Free-threaded CPython is unsupported: 3.13t does not build, and on 3.14t and later importing the module re-enables the GIL with a RuntimeWarning.

import asyncio
from object_storage_client import ObjectStorageClient

async def main():
    client = ObjectStorageClient()

    # Create a bucket (S3/GCS/Azure, or a directory for file:// URLs); success if it is already yours
    await client.create_bucket("s3://my-bucket")

    # Check whether a bucket exists (returns a bool; never raises for a miss).
    if await client.bucket_exists("s3://my-bucket"):
        print("my-bucket is present")

    # Upload data to S3
    await client.put_object("s3://my-bucket/hello.txt", b"Hello from Python!")

    # Check whether an object exists (returns a bool; never raises for a miss).
    # If you prefer the missing case to raise FileNotFoundError, use
    # get_object_metadata() or get_object() instead.
    if await client.object_exists("s3://my-bucket/hello.txt"):
        print("hello.txt is present")

    # Fetch full metadata (raises FileNotFoundError if the object is missing)
    meta = await client.get_object_metadata("s3://my-bucket/hello.txt")
    print(f"Size: {meta['size_bytes']}, type: {meta['content_type']}")

    # Download data
    data = await client.get_object("s3://my-bucket/hello.txt")
    print(f"Retrieved: {data.decode()}")

    # List objects
    items = await client.list_objects("s3://my-bucket/")
    print(f"Bucket items: {items}")

    # List a large prefix in bounded batches
    async for names in await client.list_objects_stream("s3://my-bucket/"):
        print(f"{len(names)} more items")

    # Stream data
    stream = await client.get_object_stream("s3://my-bucket/hello.txt")
    async for chunk in stream:
        print(f"Chunk size: {len(chunk)}")

    # --- Move data across providers with one client ---

    # Copy S3 -> Google Cloud Storage (source is left in place)
    await client.copy_object("s3://my-bucket/hello.txt", "gs://my-gcs-bucket/hello.txt")

    # Move GCS -> Azure Blob Storage (source is deleted afterwards)
    await client.move_object("gs://my-gcs-bucket/hello.txt", "az://my-container/hello.txt")

    # Copy Azure -> local disk for a working copy
    await client.copy_object("az://my-container/hello.txt", "file:///tmp/hello_local.txt")

    # --- Pre-signed URLs (S3/GCS/Azure): credential-free, time-limited access ---

    download_url = await client.get_pre_signed_url("s3://my-bucket/hello.txt")
    # Bind the exact Content-Length and Content-Type the client must send (S3
    # only); the store rejects uploads that don't match.
    upload_url = await client.get_pre_signed_url(
        "s3://my-bucket/upload.bin",
        method="PUT",
        expires_in_secs=900,
        content_length=1_048_576,
        content_type="application/octet-stream",
    )
    print(f"Download: {download_url}\nUpload: {upload_url}")

if __name__ == "__main__":
    asyncio.run(main())

With encryption (key bytes never reach Python):

from object_storage_client import ObjectStorageClient, Keyring

keyring = Keyring.from_file("/var/run/secrets/osc/keyring")    # reloads itself
secure = ObjectStorageClient().with_encryption(keyring)
# or directly: EncryptedObjectStorageClient(keyring, profile="dev")  # profile= is optional

await secure.put_object("s3://my-bucket/payroll.csv", b"id,salary")  # only ciphertext is stored
data = await secure.get_object("s3://my-bucket/payroll.csv")         # authenticated before it is returned
health = keyring.status()  # active key, key ages, last reload error

CLI (osc)

export CARGO_REGISTRIES_BIXORITY_INDEX="sparse+https://codeberg.org/api/packages/bixority/cargo/"
cargo install object-storage-client --registry bixority
# or: cargo install --git https://codeberg.org/bixority/object-storage-client
# or, from a checkout: cargo install --path .
osc put my_file.txt s3://my-bucket/remote_file.txt              # upload a file
osc put --recursive my_dir s3://my-bucket/remote_dir/           # upload a directory
osc get gs://my-bucket/data.json ./local_data.json              # download
osc get-stream gs://my-bucket/large_file.bin > large_file.bin   # stream to stdout; progress on stderr
osc --profile dev ls s3://my-bucket/                            # credentials from the AWS profile "dev"
osc cp s3://source-bucket/image.png az://dest-container/image.png   # copy between providers
osc mv s3://my-bucket/old_name.txt s3://my-bucket/new_name.txt
osc ls s3://my-bucket/logs/                                     # names; --url prints full object URLs
osc rm s3://my-bucket/temp_file.tmp
osc exists s3://my-bucket/report.pdf                            # prints true or false
osc mb s3://my-new-bucket                                       # create a bucket (a directory for local paths)
osc bucket-exists s3://my-bucket                                # prints true or false

# Pre-signed URLs (S3, GCS, Azure): a download link valid for the default
# 1 hour, and an upload (PUT) link valid for 15 minutes. With temporary
# credentials (SSO, an assumed role) an s3:// link stops working when that
# session ends, whatever the expiry
osc sign s3://my-bucket/report.pdf
osc sign --method PUT --expires-in 900 s3://my-bucket/upload.bin
# S3 only: the upload is rejected unless Content-Length and Content-Type match
osc sign --method PUT --content-length 1048576 \
    --content-type application/pdf s3://my-bucket/upload.pdf

get-stream writes each chunk to standard output as it arrives, so its output is complete only if osc exits 0. A failed read, or a truncated or tampered encrypted object, stops the output part way: every byte written was authenticated, but the object may be cut short. In a pipeline use set -o pipefail, or give a FILE for an all-or-nothing download.

With a keyring, put, get, get-stream, cp and mv encrypt and decrypt transparently:

umask 077                                    # keyring files must not be readable by others
osc keyring new > keyring                    # a keyring with one fresh key
osc --keyring keyring put report.csv s3://my-bucket/report.csv
osc --keyring keyring get s3://my-bucket/report.csv report.csv
osc enc inspect s3://my-bucket/report.csv    # header details; no keys needed

# Rotation: add a key, wait until every reader has it, activate it, then move
# objects off the old one (a single reader may use `osc keyring rotate`)
osc keyring add < keyring > keyring.new && mv keyring.new keyring
osc keyring activate <new key ID> < keyring > keyring.new && mv keyring.new keyring
osc --keyring keyring enc reencrypt s3://my-bucket/ --from <old key ID>

--keyring can also come from OSC_KEYRING_FILE, or from a command that prints the keyring (OSC_KEYRING_COMMAND), so the keyring never touches the disk.

Desktop browser (osc-gui)

osc-gui is a two-panel desktop browser for the same stores as osc. Each panel shows one folder, and you copy, move, rename and delete objects and whole folders within a panel or between the two. It uses the same credentials and encryption options as osc.

osc-gui showing the root folder in both panels

Install

The browser is behind the optional gui feature, so osc alone is unaffected. Install both binaries from the registry:

export CARGO_REGISTRIES_BIXORITY_INDEX="sparse+https://codeberg.org/api/packages/bixority/cargo/"
cargo install object-storage-client --registry bixority --features gui

Or from a checkout:

cargo install --path . --features gui

On Linux, osc-gui needs a Wayland session; X11 is not supported.

Run

osc-gui                                        # both panels on the current directory
osc-gui s3://my-bucket/photos/ ~/Pictures      # left and right panel
osc-gui --profile dev s3://my-bucket/          # credentials from the AWS profile "dev"
osc-gui --keyring keyring s3://my-bucket/ .    # copies encrypt and decrypt

Type any URL or path into a panel's address bar and press Enter. Buckets are not listed, so type the bucket's URL. The keys and shortcuts are listed in Desktop browser, which also covers limits and closing behaviour.

Documentation

  • Configuration: credentials and environment variables for each provider.
  • Encryption: what it protects, keyrings, Kubernetes, key rotation, responding to a key leak, the format and interop.
  • Behaviour and limits: URL rules, copy and move, deletes, file permissions, large objects, pre-signing, CLI and Python details.
  • Desktop browser: osc-gui, its keys, limits and closing.
  • Upgrading: breaking changes between releases.
  • Development and Testing.

Metadata

Release files for object-storage-client 0.4.0

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

Source distribution (sdist)

Source distribution for object-storage-client 0.4.0
File Size Uploaded Provenance Actions
object_storage_client-0.4.0.tar.gz 2.0 MB With provenance Details for object_storage_client-0.4.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for object-storage-client 0.4.0
File Actions
object_storage_client-0.4.0-cp315-cp315-win_amd64.whl CPython 3.15 CPython 3.15 Windows x86-64 Details for object_storage_client-0.4.0-cp315-cp315-win_amd64.whl
object_storage_client-0.4.0-cp315-cp315-manylinux_2_28_aarch64.whl CPython 3.15 CPython 3.15 Linux glibc 2.28+ ARM64 Details for object_storage_client-0.4.0-cp315-cp315-manylinux_2_28_aarch64.whl
object_storage_client-0.4.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.15 CPython 3.15 Linux glibc 2.17+ x86-64 Details for object_storage_client-0.4.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
object_storage_client-0.4.0-cp315-cp315-macosx_11_0_arm64.whl CPython 3.15 CPython 3.15 macOS 11.0+ ARM64 Details for object_storage_client-0.4.0-cp315-cp315-macosx_11_0_arm64.whl
object_storage_client-0.4.0-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for object_storage_client-0.4.0-cp314-cp314-win_amd64.whl
object_storage_client-0.4.0-cp314-cp314-manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ ARM64 Details for object_storage_client-0.4.0-cp314-cp314-manylinux_2_28_aarch64.whl
object_storage_client-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64 Details for object_storage_client-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
object_storage_client-0.4.0-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for object_storage_client-0.4.0-cp314-cp314-macosx_11_0_arm64.whl
object_storage_client-0.4.0-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for object_storage_client-0.4.0-cp313-cp313-win_amd64.whl
object_storage_client-0.4.0-cp313-cp313-manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ ARM64 Details for object_storage_client-0.4.0-cp313-cp313-manylinux_2_28_aarch64.whl
object_storage_client-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64 Details for object_storage_client-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
object_storage_client-0.4.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for object_storage_client-0.4.0-cp313-cp313-macosx_11_0_arm64.whl

Total release size: 77.3 MB

Release files / object_storage_client-0.4.0.tar.gz

Download URL object_storage_client-0.4.0.tar.gz
Size 2.0 MB
Tags Source
SHA-256 checksum
How to use checksums
1d94ab7fe1e528fdc52b6bec0ae270cfc7cc363140847c18514d62516620ec9c
BLAKE2b-256 checksum
How to use checksums
8451d0a086bd78b4bb38173f661031dfd080203051121788084965a687a3df55
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp315-cp315-win_amd64.whl

Download URL object_storage_client-0.4.0-cp315-cp315-win_amd64.whl
Size 6.7 MB
Tags CPython 3.15 Windows x86-64
SHA-256 checksum
How to use checksums
00d8194af4058f78e87e24c5018c994c4063198981261f0bdd1899fc71e50619
BLAKE2b-256 checksum
How to use checksums
5f8a84092315119182b682490625ce7da25dba8e9fb5260933641c15fe0e7d86
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp315-cp315-manylinux_2_28_aarch64.whl

Download URL object_storage_client-0.4.0-cp315-cp315-manylinux_2_28_aarch64.whl
Size 6.3 MB
Tags CPython 3.15 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
61a2034c6f0a8f9d320465f71411fffe97cab41ccffdd0c19cf7c9bafaae4256
BLAKE2b-256 checksum
How to use checksums
59965e003f4b202f5a7ee958af451edb1397555944cb1240055c01c81f369936
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL object_storage_client-0.4.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 6.6 MB
Tags CPython 3.15 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
aa960cfb1e30cfbde2ccca983521080316abcb4df42ad4a20982f93b979e11b8
BLAKE2b-256 checksum
How to use checksums
9c8528cc449dd8e51fc5ea00255492f4d6a0f76909c3c53e6079fc9df8c4f3f2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp315-cp315-macosx_11_0_arm64.whl

Download URL object_storage_client-0.4.0-cp315-cp315-macosx_11_0_arm64.whl
Size 5.5 MB
Tags CPython 3.15 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
a61a789bd177ada05457abca8aa25dc5071db5a21a9b4f0310b10919d898c9b9
BLAKE2b-256 checksum
How to use checksums
ce34bd6aef96e52ed565b32e979da357e34a25f8bb736dee3165e263360389c0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp314-cp314-win_amd64.whl

Download URL object_storage_client-0.4.0-cp314-cp314-win_amd64.whl
Size 6.7 MB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
deb6f3d4668af1fc027a9122ff4b1b485cad8f13177d6f00d1a2db8864d93133
BLAKE2b-256 checksum
How to use checksums
c7c17a01d990d00ae01f42a10c6783c2aeafd04783e1ec48d3a162fbbc7c0a31
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp314-cp314-manylinux_2_28_aarch64.whl

Download URL object_storage_client-0.4.0-cp314-cp314-manylinux_2_28_aarch64.whl
Size 6.3 MB
Tags CPython 3.14 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
900395ab219b5f81f69f1f2a021305f27ad943eefa4e4d5bef3a22bcedb21a07
BLAKE2b-256 checksum
How to use checksums
bddc295d00eed37061741f817a7635701236ff12a5792f0b4f72f966158979c4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL object_storage_client-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 6.6 MB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
b50424530de777933a2d7be469d3de1b74c0e60a28d1619d650413c7a37e32b5
BLAKE2b-256 checksum
How to use checksums
4e1ac52052694fed115518b3be7624cf8d50109041baf6ef65dfb5a9ac6588c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp314-cp314-macosx_11_0_arm64.whl

Download URL object_storage_client-0.4.0-cp314-cp314-macosx_11_0_arm64.whl
Size 5.5 MB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3fcbec479da4f036b3e82cf0c45261d4036803105248531052937cba062f135a
BLAKE2b-256 checksum
How to use checksums
7bd0835c26d537eef83105fd80b04a6cb9061edb0901ec8d7f2cc7988892c63d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp313-cp313-win_amd64.whl

Download URL object_storage_client-0.4.0-cp313-cp313-win_amd64.whl
Size 6.7 MB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
d9cfb6ee25b196ab6612f2676d05048e632df605a2ec9526926442c45b5bf56d
BLAKE2b-256 checksum
How to use checksums
8a02d607b828a9230a47335a4e2f5d97cad5b5fcd13000b8a732cf9f855b767f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp313-cp313-manylinux_2_28_aarch64.whl

Download URL object_storage_client-0.4.0-cp313-cp313-manylinux_2_28_aarch64.whl
Size 6.3 MB
Tags CPython 3.13 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
747dd26732928844c2e43ca793dbb891fc863cb1a259a4acb4419c03d7018718
BLAKE2b-256 checksum
How to use checksums
1d2028f238d08e7bed2c92a7020c6cb934f904f515d13a79822f571e07dc595e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL object_storage_client-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 6.6 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
d2c4a5dc646d21713be4c347c056e7b19ebc571d8a60ce795161d44339586ca5
BLAKE2b-256 checksum
How to use checksums
525aac0951e7262c453ae7d1e5def042bb6a9563e9fa0c997fdc9595c23d1706
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Release files / object_storage_client-0.4.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL object_storage_client-0.4.0-cp313-cp313-macosx_11_0_arm64.whl
Size 5.5 MB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
eaf77593115014fc7b1086050f72106c1463856741f8d8fbc98531c8c89d5c4a
BLAKE2b-256 checksum
How to use checksums
3dc95a3849a1eec4f7d5d8bb51fb37ac2d093609c5c1b65dae40c8eeccf2c8ba
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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, 2026.

Transparency log

Security for object-storage-client 0.4.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.

Full provenance

All 13 files in this release have been uploaded with provenance metadata.

Select from 13 files

Attestation for object_storage_client-0.4.0.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 Nov 4, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.4.0 This release

13 release files Full provenance

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