Skip to main content

cachekit

Python caching, batteries included

Backend-agnostic caching with intent-based decorators — circuit breaker, distributed locking, Prometheus metrics, and optional zero-knowledge encryption on a Rust-powered core. Zero config to start, any backend when you scale.

PyPI Version Python Versions codecov License: MIT



Why cachekit?

Simple to use, works out of the box.

from cachekit import cache

@cache
def expensive_function():
    return fetch_data()

That's it. You get:

Feature Description
Circuit breaker Prevents cascading failures
Distributed locking Multi-pod safety
Prometheus metrics Built-in observability
MessagePack serialization Efficient with optional compression
Zero-knowledge encryption Client-side AES-256-GCM

Quick Start

Installation

pip install cachekit

Or with uv (recommended):

uv add cachekit

Setup

With nothing configured, @cache caches in L1, in process, like lru_cache: no backend, no connection attempt, no warning.

from cachekit import cache

@cache  # nothing configured: L1-only, per process
def expensive_api_call(user_id: int):
    return fetch_user_data(user_id)

An L1-only cache is not shared between processes, holds values by reference, and is chosen at the function's first call, so configure a backend before then.

Choose a backend

cachekit exposes one decorator API over a pluggable backend abstraction. Pick the backend that fits your infrastructure — they're peers behind the same @cache API:

Backend Best for Select with
Redis Self-hosted, full control REDIS_URL / CACHEKIT_REDIS_URL
CachekitIO Managed, zero-ops (beta) CACHEKIT_API_KEY
Memcached High-throughput, existing infra CACHEKIT_MEMCACHED_SERVERS
File / L1-only Local dev, tests, no external deps CACHEKIT_FILE_CACHE_DIR / nothing (or backend=None)
# Run Redis locally or use your existing infrastructure
export REDIS_URL="redis://localhost:6379"
from cachekit import cache

@cache  # REDIS_URL set: L1 + Redis, shared across processes
def expensive_api_call(user_id: int):
    return fetch_user_data(user_id)

More Backends

CachekitIO — Managed SaaS (Beta)
import os
from cachekit import cache

# Set your CachekitIO API key
# export CACHEKIT_API_KEY="your-api-key"  # pragma: allowlist secret

@cache.io()  # Uses CachekitIO SaaS backend — no Redis to manage
def expensive_api_call(user_id: int):
    return fetch_user_data(user_id)

cachekit.io is in closed beta — request access to get started.

How fresh a cachekit.io read is, and how long a deleted project's data stays readable: Consistency and Deletion.

Memcached — Optional
from cachekit import cache
from cachekit.backends.memcached import MemcachedBackend

# pip install cachekit[memcached]

backend = MemcachedBackend()  # Defaults to 127.0.0.1:11211

@cache(backend=backend)
def expensive_api_call(user_id: int):
    return fetch_user_data(user_id)

Requires: pip install cachekit[memcached] or uv add cachekit[memcached]


CachekitIO Cloud (Beta) Managed caching with zero infrastructure. L1+L2 caching, circuit breaker, and automatic failover — no Redis to manage. cachekit.io is in closed beta — request access to get started.


Intent-Based Optimization

cachekit provides preset configurations for different use cases:

# Speed-critical: trading, gaming, real-time
@cache.minimal
def get_price(symbol: str):
    return fetch_price(symbol)

# Reliability-critical: payments, APIs
@cache.production
def process_payment(amount):
    return payment_gateway.charge(amount)

# Security-critical: PII, medical, financial (needs a key: master_key= or CACHEKIT_MASTER_KEY)
@cache.secure(master_key=secret_key)
def get_user_profile(user_id: int):
    return db.fetch_user(user_id)

Setting CACHEKIT_MASTER_KEY instead of passing master_key= means every preset except @cache.secure and @cache.local must state its intent (encryption=False for plaintext), or it raises ConfigurationError at decoration: the key is a key source, never an on switch.

Feature @cache.minimal @cache.dev @cache.test @cache.production @cache.secure
Default TTL 300 s 300 s 300 s 600 s 600 s
Circuit Breaker - ✅ - ✅ ✅
Backpressure ✅ ✅ - ✅ ✅
Integrity Checking - ✅ - ✅ ✅ 🔒
Encryption - - - - ✅ Required
L1 SWR (L1-only mode) - ✅ - ✅ -
Prometheus Metrics - -¹ - ✅ ✅
Structured Logging - ✅ - ✅ ✅
Backend unreachable² Function runs, no error Function runs, no error Function runs, no error Function runs, no error Function runs, no error
Use Case High throughput Local debugging Deterministic tests Production reliability Compliance/security

¹ @cache.dev exports no Prometheus metrics except circuit_breaker_state, which is recorded for every function whose circuit breaker is enabled.

² A backend that is down or unreachable never raises to the caller, on any preset (@cache.io included): the call logs the failure and runs your function. What gets cached meanwhile is in Connection Errors.

🔒 @cache.secure forces integrity_checking=True — passing integrity_checking=False raises ConfigurationError at decoration, including as an override next to config=DecoratorConfig.secure(...). Its encryption is fixed the same way: encryption= raises ConfigurationError on @cache.secure and next to config=DecoratorConfig.secure(...), so pass fail_closed= and the other encryption options to the preset itself. @cache.secure also rejects config=; the RORO form is @cache(config=DecoratorConfig.secure(...)).

Default TTL follows the cross-SDK intent-preset spec (@cache.io 3600 s) — the same numbers as cachekit-rs and cachekit-ts. ttl= overrides it; ttl=None is the explicit never-expire opt-in (details).

Cross-process L1 eviction is not a preset feature: every preset's invalidate_cache() deletes from L1 and L2 alike, and evicting other processes' L1 copies is one process-wide opt-in, CACHEKIT_INVALIDATION_LISTENER_ENABLED (L1 invalidation).

L1 SWR (within-TTL background refresh) runs only in L1-only mode (backend=None) — with a backend configured it has no effect. @cache.io additionally ships past-TTL SWR via stale_ttl (docs).

@cache.io() mirrors @cache.production (full reliability + observability) but routes to the managed CachekitIO SaaS backend instead of Redis. @cache.local() is a Python-only, SDK-local preset: a separate in-process path backed by ObjectCache (raw object references, entry-count LRU, no serialization) — the reliability and encryption features listed above do not apply to it.

Additional Presets: @cache.dev and @cache.test

@cache.dev and @cache.test are Python-only, SDK-local presets. See the comparison table above for the exact feature set of each preset.

# Development: verbose logging, integrity checks on, Prometheus off except circuit_breaker_state
@cache.dev
def debug_expensive_call():
    return complex_computation()

# Testing: deterministic, all protections off (no circuit breaker, no backpressure)
@cache.test
def test_cached_function():
    return fixed_test_value()

Architecture

┌─────────────────────────────────────────────────────────────┐
│                        Application                          │
├─────────────────────────────────────────────────────────────┤
│                     @cache Decorator                        │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────┐  │
│  │   Circuit   │  │  Adaptive   │  │    Distributed      │  │
│  │   Breaker   │  │  Timeouts   │  │      Locking        │  │
│  └─────────────┘  └─────────────┘  └─────────────────────┘  │
├─────────────────────────────────────────────────────────────┤
│  L1 Cache (In-Memory)  │  L2 Cache (Pluggable Backend)      │
│       in-process       │  Redis / CachekitIO / File /       │
│                        │  Memcached: one backend round trip │
├─────────────────────────────────────────────────────────────┤
│                    Rust Core (PyO3)                         │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────┐  │
│  │    LZ4      │  │  xxHash3    │  │    AES-256-GCM      │  │
│  │ Compression │  │  Checksums  │  │    Encryption       │  │
│  └─────────────┘  └─────────────┘  └─────────────────────┘  │
└─────────────────────────────────────────────────────────────┘

Performance

What a call costs inside your process, from the wall-clock guards in tests/performance/ run on a GitHub-hosted ubuntu-latest runner (AMD EPYC 7763, 4 vCPUs) with CPython 3.14.7. Each figure is the mean of five run medians with its 95% band.

Path Time per call
@cache(backend=None) L1 hit, 100-user nested dict (23.5 KB as MessagePack) 0.906 ± 0.007 µs
@cache(backend=None) L1 hit, 10K-row DataFrame 0.91 ± 0.01 µs
L1 hit with an L2 backend configured, same dict 310 ± 20 µs
Redis L2 hit with L1 disabled, same dict, Redis in a container on the same machine 551 ± 18 µs
  • With no backend, L1 keeps the returned object itself, whatever the payload's size, and a repeat call with a few short scalar arguments finds its cache key in a per-function memo instead of building it again (which calls). Any other call builds its key every time, as does every call to a function with a backend.
  • With an L2 backend, L1 holds the serialized bytes and every hit deserializes them: for this dict, about 340 times the L1-only hit. Encryption adds a decrypt to each such hit; on this run that added 10 ± 21 µs, inside the noise.
  • An L2 hit adds the backend's round trip. A Redis on another machine adds its network latency to the last row.

Hosted runners come with other CPU models too: in a run of an earlier commit, an EPYC 9V45 runner took about half as long on every row, and other machines give other figures. The Performance Guide names the guard behind each figure and how to run it, and the repository's Bench workflow repeats the run.


Features

Production Hardened

  • Circuit breaker with graceful degradation
  • Connection pooling with thread affinity
  • CachekitIO keeps idle connections pooled until the server closes them, with TCP keepalive probes, so a request after a pause skips a new TLS handshake
  • Distributed locking prevents cache stampedes
  • Pluggable backend abstraction (Redis, CachekitIO, File, Memcached, custom)
  • Untrusted-decode bounds: nesting depth and header-declared allocation are capped on every cache read (a forged entry is a bounded cache miss), verified against the protocol's shared decode-bounds.json vectors

Smart Serialization

Serializer Speed Use Case
StandardSerializer ★★★★☆ General Python types; not NumPy arrays or pandas objects
OrjsonSerializer ★★★★★ JSON APIs — requires cachekit[json]
ArrowSerializer — pandas DataFrames (columnar, exact round trip)
+ Encryption ★★★★☆ Any serializer above, AES-256-GCM encrypted: @cache.secure(master_key=..., serializer=...)
Serializer Examples
from cachekit.serializers import OrjsonSerializer, ArrowSerializer

# Fast JSON for API responses
@cache.production(serializer=OrjsonSerializer())
def get_api_response(endpoint: str):
    return {"status": "success", "data": fetch_api(endpoint)}

# Columnar DataFrames (Arrow IPC, zstd-compressed by default)
@cache(serializer=ArrowSerializer())
def get_large_dataset(date: str):
    return pd.read_csv(f"data/{date}.csv")

Encrypted DataFrames go through @cache.secure, which takes any serializer whose class declares cross_sdk_compatible = True (details). A file backend keeps this example self-contained; production uses Redis or cachekit.io:

import tempfile
from cachekit.backends.file import FileBackend, FileBackendConfig
from cachekit.serializers import ArrowSerializer

calls = 0

@cache.secure(
    master_key=secret_key,
    serializer=ArrowSerializer(),
    backend=FileBackend(FileBackendConfig(cache_dir=tempfile.mkdtemp())),
)
def get_patient_data(hospital_id: int):
    global calls
    calls += 1
    return pd.DataFrame({"hospital_id": [hospital_id], "patients": [42]})

get_patient_data(7)
get_patient_data(7)  # second call is served from the encrypted cache
assert calls == 1

Integrity Checking

Each checksum is an 8-byte digest, plus one pass over the payload on each write and read. What enable_integrity_checking=False changes depends on the serializer, and for AutoSerializer on the value:

Serializer Checking on (default) Checking off
StandardSerializer, and AutoSerializer for values other than the two below MessagePack in an LZ4 envelope that carries the checksum Plain MessagePack: no checksum, no LZ4
AutoSerializer, NumPy arrays The checksum, then the raw array bytes (never compressed) The raw array bytes
AutoSerializer, pandas DataFrames with pyarrow installed, and ArrowSerializer The checksum, then the Arrow IPC data No change: Arrow always checks
OrjsonSerializer The checksum, then the JSON Plain JSON

Where the switch drops the LZ4 envelope, an entry gets larger only when LZ4 saved more than the envelope's overhead of about 25 to 30 bytes; otherwise it stays the same size or gets smaller. Measure on your own payloads before you trade that.

Security

Key rotation: keep a retiring key readable with CACHEKIT_PREVIOUS_MASTER_KEYS (comma-separated hex, max 3 decrypt-only keys) while new writes use CACHEKIT_MASTER_KEY. A one-deploy key swap is not zero-miss; follow the key rotation runbook, including its Before You Rotate checks. CK-framed entries are selected by exact key fingerprint — never trial decryption; Interop-mode entries carry no CK frame and attempt keyring keys sequentially instead.

cachekit employs comprehensive security tooling:

  • Dependency Security: cargo-deny for license compliance + cargo-audit for RustSec scanning
  • Formal Verification: Kani proves correctness of compression, checksums, encryption
  • Runtime Analysis: Miri + sanitizers for memory safety
  • Fuzzing: Coverage-guided testing with >80% code coverage
  • Zero CVEs: Continuous vulnerability scanning
Security Commands
make security-install  # Install security tools (one-time)
make security-fast     # Run fast checks (< 3 min)

Security Tiers:

Tier Time Coverage
Fast < 3 min Vulnerability scanning, license checks, linting
Medium < 15 min Unsafe code analysis (cargo-geiger)
Deep < 2 hours Formal verification, extended fuzzing, full sanitizers

See SECURITY.md for vulnerability reporting and detailed documentation.

Monitoring & Observability

  • Per-function statistics - cache_info() on every decorated function, modelled on functools.lru_cache
  • Prometheus metrics - Recorded by default (your app owns exposition)
  • Structured logging - Context-aware, per-operation fields
  • Health checks - Comprehensive status endpoints

Every decorated function exposes cache_info(), returning a CacheInfo named tuple with hit/miss counts, the L1/L2 split, and average backend latency:

@cache()
def get_score(x):
    return x ** 2

get_score(2)
get_score(2)  # served from cache

info = get_score.cache_info()
# CacheInfo has 9 fields: hits, misses, l1_hits, l2_hits, maxsize,
# currsize, l2_avg_latency_ms, last_operation_at, session_id
assert (info.hits, info.misses) == (1, 1)  # the second call was a hit
assert info.l1_hits + info.l2_hits == info.hits  # every hit is L1 or L2

maxsize and currsize are always None (the cache lives in an external store, not a bounded in-process dict); they exist only for lru_cache API parity. See the API Reference for the full field reference and a sample stats endpoint, and the Prometheus Metrics guide for metric names and exposition setup.

Thread Safety Details

Free-threaded CPython (3.15t, 3.14t): the core suites run green on free-threaded 3.14 and 3.15 with the GIL verified disabled (CI job test-freethreaded), and the Rust extension declares free-threaded safety (gil_used = false). From the release after 0.24.1, 3.15t has a wheel: the 3.15+ wheel is abi3t, so it installs on 3.15t without a Rust toolchain (pip 26.1+ or uv 0.11.3+). 3.14t is tested but has no wheel (it builds from source). Free-threaded builds are not officially supported yet — blocked upstream on orjson (no free-threaded wheels) and hiredis (re-enables the GIL on import; cachekit loads redis-py only for its Redis backend, and keeps hiredis out there, so redis-py uses its pure-Python parser). See measured performance results and the full concurrency audit: docs/free-threading.md.

Per-Function Statistics:

  • Statistics tracked per function identity (module.qualname), shared across all calls and across re-decorations of the same function
  • Thread-safe: every count is exact (L1 hits on an atomic counter, everything else under an RLock), and all methods are safe for concurrent access
  • Fork-safe: a forked child starts with zeroed counters and its own session ID
from concurrent.futures import ThreadPoolExecutor

@cache()
def expensive_func(x):
    return x ** 2

# All threads share same stats
with ThreadPoolExecutor(max_workers=10) as executor:
    results = list(executor.map(expensive_func, range(100)))

info = expensive_func.cache_info()
# CacheInfo(hits=..., misses=..., l1_hits=..., l2_hits=...,
#           maxsize=None, currsize=None, l2_avg_latency_ms=...,
#           last_operation_at=..., session_id=...)

Documentation

Start Here

Guide Description
Comparison Guide How cachekit compares to lru_cache, aiocache, cachetools
Getting Started Progressive tutorial from basics to advanced
API Reference Complete API documentation
Skyline (live example) Canonical example project: this SDK ingests the Bluesky firehose and writes the analytics entries a TypeScript edge Worker serves live, on one shared interop namespace

Feature Deep Dives

Feature Description
Serializer Guide ArrowSerializer vs StandardSerializer benchmarks
Circuit Breaker Prevent cascading failures
Distributed Locking Cache stampede prevention
Prometheus Metrics Built-in observability
Zero-Knowledge Encryption Client-side security
Interop Mode Cross-SDK cache sharing with cachekit-ts/rs
L1 Invalidation & SWR Invalidation scope (incl. cross-process whole-function on tenant-scoped Redis from the environment or RedisBackendProvider), opt-in cross-process L1 eviction, stale-while-revalidate
Reference Caching @cache.local() for non-serializable objects
Rust Serialization ByteStorage layer: LZ4, xxHash3, AES-256-GCM
SSRF Protection URL allowlisting for the CachekitIO backend
Write-Behind Opt-in write_behind=True: a miss returns before its L2 write lands

Configuration

Environment Variables

# Backend selection: set exactly ONE of CACHEKIT_REDIS_URL, CACHEKIT_API_KEY,
# CACHEKIT_MEMCACHED_SERVERS, CACHEKIT_FILE_CACHE_DIR. Two or more is a ConfigurationError at
# first call, and decorators relying on env auto-detection run uncached (docs/backends/README.md).
# REDIS_URL is only a fallback and never conflicts. With none of them set, decorators cache
# L1-only, in process (encrypted and interop decorators still use localhost Redis).

# Redis Connection (priority: CACHEKIT_REDIS_URL > REDIS_URL)
CACHEKIT_REDIS_URL="redis://localhost:6379"  # Primary (preferred)
REDIS_URL="redis://localhost:6379"           # Fallback

# CachekitIO SaaS Backend (closed beta — request access at cachekit.io)
# For @cache.io() next to Redis, pass api_key= from your secret store instead.
# CACHEKIT_API_KEY="your-api-key"  # pragma: allowlist secret
CACHEKIT_API_URL="https://api.cachekit.io"  # Default SaaS endpoint

# Memcached Backend (optional: pip install cachekit[memcached])
# CACHEKIT_MEMCACHED_SERVERS='["mc1:11211", "mc2:11211"]'  # Default: 127.0.0.1:11211
CACHEKIT_MEMCACHED_CONNECT_TIMEOUT=2.0                   # Default: 2.0 seconds
CACHEKIT_MEMCACHED_TIMEOUT=1.0                            # Default: 1.0 seconds
CACHEKIT_MEMCACHED_KEY_PREFIX="myapp:"                    # Default: "" (none)

# Optional Configuration
CACHEKIT_MAX_VALUE_SIZE=104857600
CACHEKIT_ARROW_COMPRESSION=zstd

Development

git clone https://github.com/cachekit-io/cachekit-py.git
cd cachekit-py
uv sync && make install
make quick-check  # format + lint + critical tests

See CONTRIBUTING.md for full development guidelines.


Requirements

Component Version
Python 3.11+

License

MIT License - see LICENSE for details.


Metadata

Release files for cachekit 0.25.1

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

Source distribution (sdist)

Source distribution for cachekit 0.25.1
File Size Uploaded Provenance Actions
cachekit-0.25.1.tar.gz 453.0 kB With provenance Details for cachekit-0.25.1.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for cachekit 0.25.1
File Actions
cachekit-0.25.1-cp315-abi3.abi3t-win_amd64.whl CPython 3.15 abi3t, abi3 Windows x86-64 Details for cachekit-0.25.1-cp315-abi3.abi3t-win_amd64.whl
cachekit-0.25.1-cp315-abi3.abi3t-manylinux_2_28_aarch64.whl CPython 3.15 abi3, abi3t Linux glibc 2.28+ ARM64 Details for cachekit-0.25.1-cp315-abi3.abi3t-manylinux_2_28_aarch64.whl
cachekit-0.25.1-cp315-abi3.abi3t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.15 abi3t, abi3 Linux glibc 2.17+ x86-64 Details for cachekit-0.25.1-cp315-abi3.abi3t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
cachekit-0.25.1-cp315-abi3.abi3t-macosx_11_0_arm64.whl CPython 3.15 abi3, abi3t macOS 11.0+ ARM64 Details for cachekit-0.25.1-cp315-abi3.abi3t-macosx_11_0_arm64.whl
cachekit-0.25.1-cp315-abi3.abi3t-macosx_10_12_x86_64.whl CPython 3.15 abi3, abi3t macOS 10.12+ x86-64 Details for cachekit-0.25.1-cp315-abi3.abi3t-macosx_10_12_x86_64.whl
cachekit-0.25.1-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for cachekit-0.25.1-cp314-cp314-win_amd64.whl
cachekit-0.25.1-cp314-cp314-manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ ARM64 Details for cachekit-0.25.1-cp314-cp314-manylinux_2_28_aarch64.whl
cachekit-0.25.1-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 cachekit-0.25.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
cachekit-0.25.1-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for cachekit-0.25.1-cp314-cp314-macosx_11_0_arm64.whl
cachekit-0.25.1-cp314-cp314-macosx_10_12_x86_64.whl CPython 3.14 CPython 3.14 macOS 10.12+ x86-64 Details for cachekit-0.25.1-cp314-cp314-macosx_10_12_x86_64.whl
cachekit-0.25.1-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for cachekit-0.25.1-cp313-cp313-win_amd64.whl
cachekit-0.25.1-cp313-cp313-manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ ARM64 Details for cachekit-0.25.1-cp313-cp313-manylinux_2_28_aarch64.whl
cachekit-0.25.1-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 cachekit-0.25.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
cachekit-0.25.1-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for cachekit-0.25.1-cp313-cp313-macosx_11_0_arm64.whl
cachekit-0.25.1-cp313-cp313-macosx_10_12_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.12+ x86-64 Details for cachekit-0.25.1-cp313-cp313-macosx_10_12_x86_64.whl
cachekit-0.25.1-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for cachekit-0.25.1-cp312-cp312-win_amd64.whl
cachekit-0.25.1-cp312-cp312-manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ ARM64 Details for cachekit-0.25.1-cp312-cp312-manylinux_2_28_aarch64.whl
cachekit-0.25.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64 Details for cachekit-0.25.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
cachekit-0.25.1-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for cachekit-0.25.1-cp312-cp312-macosx_11_0_arm64.whl
cachekit-0.25.1-cp312-cp312-macosx_10_12_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.12+ x86-64 Details for cachekit-0.25.1-cp312-cp312-macosx_10_12_x86_64.whl
cachekit-0.25.1-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for cachekit-0.25.1-cp311-cp311-win_amd64.whl
cachekit-0.25.1-cp311-cp311-manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ ARM64 Details for cachekit-0.25.1-cp311-cp311-manylinux_2_28_aarch64.whl
cachekit-0.25.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64 Details for cachekit-0.25.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
cachekit-0.25.1-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for cachekit-0.25.1-cp311-cp311-macosx_11_0_arm64.whl
cachekit-0.25.1-cp311-cp311-macosx_10_12_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.12+ x86-64 Details for cachekit-0.25.1-cp311-cp311-macosx_10_12_x86_64.whl

Total release size: 18.7 MB

Release files / cachekit-0.25.1.tar.gz

Download URL cachekit-0.25.1.tar.gz
Size 453.0 kB
Tags Source
SHA-256 checksum
How to use checksums
29b059872b18dd50c0aee4ec946180690970c08f4ebb5ade8337ff8823a07f4f
BLAKE2b-256 checksum
How to use checksums
affbdde7c9f1c7b74e3a19f4ec125e01950da95e20f98de9d0d4c86d7ffc31eb
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp315-abi3.abi3t-win_amd64.whl

Download URL cachekit-0.25.1-cp315-abi3.abi3t-win_amd64.whl
Size 672.2 kB
Tags CPython 3.15 Windows x86-64 abi3 abi3t
SHA-256 checksum
How to use checksums
ba262aa280e5f5bfc860a794689e773c293387a4b06b627156890deb2c080c61
BLAKE2b-256 checksum
How to use checksums
bd5a7cbffc934d6c61cb2e53b1e6dca0e18466c53d9c3242e555b33202876a25
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp315-abi3.abi3t-manylinux_2_28_aarch64.whl

Download URL cachekit-0.25.1-cp315-abi3.abi3t-manylinux_2_28_aarch64.whl
Size 747.8 kB
Tags CPython 3.15 Linux glibc 2.28+ ARM64 abi3 abi3t
SHA-256 checksum
How to use checksums
b2e0e4335c8a2693296488358b92401dad54a82b62ec78d98a8bcb447da46747
BLAKE2b-256 checksum
How to use checksums
cbecd33b9c20616756c96498af82254164e57112726b9c15dd4e987b62ef063a
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp315-abi3.abi3t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL cachekit-0.25.1-cp315-abi3.abi3t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 767.0 kB
Tags CPython 3.15 Linux glibc 2.17+ x86-64 abi3 abi3t
SHA-256 checksum
How to use checksums
66cb19ce66fc7a5e4f7cf84baf5752bcd556b403a6357c3df2dda4885cf95aa2
BLAKE2b-256 checksum
How to use checksums
0577f820028fdc087b5bf31e9f40bb2ebdca0d09f27690ebbd216be926e8cc6d
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp315-abi3.abi3t-macosx_11_0_arm64.whl

Download URL cachekit-0.25.1-cp315-abi3.abi3t-macosx_11_0_arm64.whl
Size 725.4 kB
Tags CPython 3.15 abi3 abi3t macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
7a90186abe34f5d7cb5f111987b2dc2a72d23c8d6c22457295bcb292472fb8fd
BLAKE2b-256 checksum
How to use checksums
7cc9ecfb0237904596b2e4611e78e2c3c5641083eb94b01682db34f71673b3e3
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp315-abi3.abi3t-macosx_10_12_x86_64.whl

Download URL cachekit-0.25.1-cp315-abi3.abi3t-macosx_10_12_x86_64.whl
Size 750.5 kB
Tags CPython 3.15 abi3 abi3t macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
fc7ad007a5a1c906a457fe33cd17b842cf835ffe80ff3499a10b47b03a256847
BLAKE2b-256 checksum
How to use checksums
789176e8a5490e20cc7dc25a334cfbdd571db069b4c3b029c11b86c926beb1ff
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp314-cp314-win_amd64.whl

Download URL cachekit-0.25.1-cp314-cp314-win_amd64.whl
Size 668.4 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
bec5cfc832f0202cc71d946e8cc7eeb11cc42fbef35571082c1b9acb8919d1a0
BLAKE2b-256 checksum
How to use checksums
8b624ea0c86114c0e5945f422fd456e24c7525871229379ca5adb2f7251dc1d3
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp314-cp314-manylinux_2_28_aarch64.whl

Download URL cachekit-0.25.1-cp314-cp314-manylinux_2_28_aarch64.whl
Size 744.8 kB
Tags CPython 3.14 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
75102c4514aa431f5f7eba78b217511ba7842766c44f75b92a9e6fd83691ac72
BLAKE2b-256 checksum
How to use checksums
ac03d36dcce088af095337c52efbb104f5311d5f1d3145dbc23585c90be9087b
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL cachekit-0.25.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 764.3 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
3f92b2459da77c581c45b39f6270b54ae8015204e7d6422391843675793413ae
BLAKE2b-256 checksum
How to use checksums
4287a73c0ba23aa05a51478146b008d35ea0c17d2a57f1d430cacf921c75a0e1
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp314-cp314-macosx_11_0_arm64.whl

Download URL cachekit-0.25.1-cp314-cp314-macosx_11_0_arm64.whl
Size 722.2 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
4faa7c30fd9ff4088e3e5b6c7188600e6798f36c21455a4cf79ec416e181d9d6
BLAKE2b-256 checksum
How to use checksums
caed651a063e6f9b6dac04844d8e087d7e97564fc37bc67c64a3f8342a2a10d4
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp314-cp314-macosx_10_12_x86_64.whl

Download URL cachekit-0.25.1-cp314-cp314-macosx_10_12_x86_64.whl
Size 747.8 kB
Tags CPython 3.14 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
034e94e6a2d7340f675deb87b566e0acbf930756f578b77d54320d4a90c57550
BLAKE2b-256 checksum
How to use checksums
3e33a26196071d70876024629b71b1e4f38f6ff942ae8c2182026476f016bbed
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp313-cp313-win_amd64.whl

Download URL cachekit-0.25.1-cp313-cp313-win_amd64.whl
Size 672.3 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
ef00255e525b6230b572750c44f497f9be66217014dc7f312cb48f6e61e7eb80
BLAKE2b-256 checksum
How to use checksums
5a81e01050e743c87fa2064dbfeae2ba6c50aa24c98845394725a05e12fc1ecb
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp313-cp313-manylinux_2_28_aarch64.whl

Download URL cachekit-0.25.1-cp313-cp313-manylinux_2_28_aarch64.whl
Size 746.4 kB
Tags CPython 3.13 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
1d55d831790e55068be29354b7d0e193f6a7e19171b1df0e36ed2dfde92e1d77
BLAKE2b-256 checksum
How to use checksums
fe82af820f43324711b385eca1fa35d855c1b54c72e2c25ce2bda20c1b8bd10a
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL cachekit-0.25.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 766.3 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
d22570084e7f87d86b32181ad8f8c7eaf03d60057cafacf4bd47516fc6b8fafc
BLAKE2b-256 checksum
How to use checksums
ef5efccba4cbd68d6419fa3525c0fe30d2f5627547a44a35e08c24be0f8a41c7
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp313-cp313-macosx_11_0_arm64.whl

Download URL cachekit-0.25.1-cp313-cp313-macosx_11_0_arm64.whl
Size 722.3 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
a9255b38778421e0335514c17e14113def85b421510e8890bfe78c96751040d5
BLAKE2b-256 checksum
How to use checksums
432a63c09e1453c023ccdde80f115ab2f255d556d6d84e1a0efc586ddbc39f29
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp313-cp313-macosx_10_12_x86_64.whl

Download URL cachekit-0.25.1-cp313-cp313-macosx_10_12_x86_64.whl
Size 747.8 kB
Tags CPython 3.13 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
1bd27fa022f27697d4afe77a3b50cbc1979ed38930161d9208a5bc244c69b73a
BLAKE2b-256 checksum
How to use checksums
4cce3d23b266fa2c4af039d34c280e587b85ac411d40d09f7acf2a897fa8d6d1
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp312-cp312-win_amd64.whl

Download URL cachekit-0.25.1-cp312-cp312-win_amd64.whl
Size 671.8 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
4e4eb525d30a589ff6f9e8e015dd7e88822ded123507987dd8ff5bc28fc63a78
BLAKE2b-256 checksum
How to use checksums
2946832bd1d8decb1bc2268d41e64c488a1aa2ccfea354db177b6f19795ecc19
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp312-cp312-manylinux_2_28_aarch64.whl

Download URL cachekit-0.25.1-cp312-cp312-manylinux_2_28_aarch64.whl
Size 745.5 kB
Tags CPython 3.12 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
a8dd204c03ae8daf423980eb222698e281446cf3ee4388a0789d961ba70be7a7
BLAKE2b-256 checksum
How to use checksums
e96c5741f65f66e7ebf659d8752f8574b5f7e7aa7e0c43ef367f514100a7f4bd
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL cachekit-0.25.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 765.7 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
1debe785d438f056cd48f674671d609cce6949e02685e1e0f2be0fe52fbd3e1e
BLAKE2b-256 checksum
How to use checksums
026635e5bf0e00cd8396e41c56f0d9b5b279a2978d38bbd4c9e7545eb7f2d341
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp312-cp312-macosx_11_0_arm64.whl

Download URL cachekit-0.25.1-cp312-cp312-macosx_11_0_arm64.whl
Size 721.9 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
52725f0395decccd1a9c5137fe460dc8dd736f4a49f4ddf2ce46bed23bd310f8
BLAKE2b-256 checksum
How to use checksums
4f7850f5f0fdb771e14dc01f03ff3a3d0db1d17288ef6dec5a9c3b3395413f42
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp312-cp312-macosx_10_12_x86_64.whl

Download URL cachekit-0.25.1-cp312-cp312-macosx_10_12_x86_64.whl
Size 747.3 kB
Tags CPython 3.12 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
60dc2f4051a0c5ace7ab92d2b349f69e04602357815dd3233854abb2204f0a21
BLAKE2b-256 checksum
How to use checksums
00f44288f8d494943209bba9020bdfc0348ad6b5e6ed9f88886b3677e1937b74
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp311-cp311-win_amd64.whl

Download URL cachekit-0.25.1-cp311-cp311-win_amd64.whl
Size 670.0 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
d629c47032da68d441771de2968bb5a2687a1f2d276853542401bcbe2eec7fda
BLAKE2b-256 checksum
How to use checksums
287747367754e4a0dfa764dc92cf03dd7a6f6edb4ea35a317509a8a05712ee74
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp311-cp311-manylinux_2_28_aarch64.whl

Download URL cachekit-0.25.1-cp311-cp311-manylinux_2_28_aarch64.whl
Size 745.3 kB
Tags CPython 3.11 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
fcf7c286b4deb84b31e116f52522d2bd2f90937de928bcaa4ea009c14142458e
BLAKE2b-256 checksum
How to use checksums
7ece0928edec5319a5fe914c68ca2e3adc9e56c3533253d0c457f6113a7e8de9
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL cachekit-0.25.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 764.0 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
c2fa98a91ff4f0e98be2665dc5e89eca2ac7bd272eb23ca167d16c51f85c7694
BLAKE2b-256 checksum
How to use checksums
18a2b1ba83068b6613134ba3c9fe9df65f7dfc2373245e445be2f6a7ea33627f
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp311-cp311-macosx_11_0_arm64.whl

Download URL cachekit-0.25.1-cp311-cp311-macosx_11_0_arm64.whl
Size 724.8 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
0c98794edc2e881653cf52bb5289c652432e4e8cd286a3d7a85c318c51a9d8be
BLAKE2b-256 checksum
How to use checksums
2b782aeef54a2481f1b6e5e741c2e651f0b04f8f584d6c1cd1ef95ebeb779b18
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 Oct 30, 2026.

Transparency log

Release files / cachekit-0.25.1-cp311-cp311-macosx_10_12_x86_64.whl

Download URL cachekit-0.25.1-cp311-cp311-macosx_10_12_x86_64.whl
Size 747.2 kB
Tags CPython 3.11 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
32c778adf2444409fe79daed7697a4da509d36b92cb4e55506decab50f1a82c4
BLAKE2b-256 checksum
How to use checksums
eb55dc420a3599dd75cfd693a16e551fc9bff1c1e76d622e8bf27592b008ac5b
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 Oct 30, 2026.

Transparency log

Security for cachekit 0.25.1

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 26 files in this release have been uploaded with provenance metadata.

Select from 26 files

Attestation for cachekit-0.25.1.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 30, 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.25.1 This release

26 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