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()

With nothing configured, that plain @cache caches in process memory (L1) only: no backend, no distributed lock, no encryption. Configure a backend and pick a preset, and you get:

Feature Description
Circuit breaker Prevents cascading failures
Distributed locking Multi-pod safety (async functions, on a backend that supports it)
Prometheus metrics Built-in observability
MessagePack serialization Efficient with optional compression
Zero-knowledge encryption Client-side AES-256-GCM, opt-in (@cache.secure)

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
CacheKit Cloud Managed, zero-ops (closed 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

CacheKit Cloud — Managed (Closed Beta)
import os
from cachekit import cache

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

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

CacheKit Cloud is in closed beta: sign-up is by waitlist at dash.cachekit.io.

During the beta the backend reports hit counts and L1 hit latency to CacheKit Cloud by default; CACHEKIT_TELEMETRY=false turns that off (Telemetry).

How fresh a CacheKit Cloud 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]


CacheKit Cloud (Closed Beta) Managed caching with zero infrastructure. L1+L2 caching, circuit breaker, and automatic failover — no Redis to manage. CacheKit Cloud is in closed beta: sign-up is by waitlist at dash.cachekit.io.


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

¹ A preset with a ✅ records get and set operations only when it has a backend: in L1-only mode it records none. @cache.dev records none of them: it sets enable_prometheus_metrics=False. Every preset still records the series that ignore MonitoringConfig, such as circuit_breaker_state. See Which Decorators Record.

² 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 CacheKit Cloud 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, no cache-operation Prometheus series
@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 / CacheKit Cloud / 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. The two L1-only rows come from a later run on the same CPU model and Python as the other two.

Path Time per call
@cache(backend=None) L1 hit, 100-user nested dict (23.5 KB as MessagePack) 0.341 ± 0.001 µs
@cache(backend=None) L1 hit, 10K-row DataFrame 0.34 ± 0.00 µs
L1 hit with an L2 backend configured, same dict 284 ± 2 µs
Redis L2 hit with L1 disabled, same dict, Redis in a container on the same machine 539 ± 3 µ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 is answered by one call into the Rust extension that takes no lock (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 830 times the L1-only hit. This run predates the Rust decode every such hit now runs, which bounds and decodes the MessagePack in one pass at about half the instructions. Encryption adds a decrypt to each such hit; this run measured the difference at 9.3 ± 1.0 µs.
  • 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
  • The CacheKit Cloud backend 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 guards against cache stampedes across pods, best effort (async functions, on a backend that supports it)
  • Pluggable backend abstraction (Redis, CacheKit Cloud, 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 Cloud:

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 by a decorator with a backend (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). 3.15t has a wheel: the 3.15+ wheel is abi3t, so it installs on 3.15t without a Rust toolchain (with a recent pip or uv). 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 CacheKit Cloud 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 decorators still use localhost Redis; interop decorators refuse
# any Redis resolved here, which is tenant-prefixed, and need backend=RedisBackend()).

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

# CacheKit Cloud backend (closed beta: join the waitlist at https://dash.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 CacheKit Cloud 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.26.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 cachekit 0.26.0
File Size Uploaded Provenance Actions
cachekit-0.26.0.tar.gz 501.3 kB With provenance Details for cachekit-0.26.0.tar.gz

Built distributions (wheels)

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

Total release size: 20.8 MB

Release files / cachekit-0.26.0.tar.gz

Download URL cachekit-0.26.0.tar.gz
Size 501.3 kB
Tags Source
SHA-256 checksum
How to use checksums
8b1acf06f758c8b61bec4b05bd40f4377d200b95627d0a9b363b8b19fec0b3c2
BLAKE2b-256 checksum
How to use checksums
91a89b373d53f1e14bbe770d6a73990d07be34fa3175342793d022b8aebe217d
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp315-abi3.abi3t-win_amd64.whl
Size 746.6 kB
Tags CPython 3.15 Windows x86-64 abi3 abi3t
SHA-256 checksum
How to use checksums
daf104223004a7de5aa6c4977e922c7af7e7a40095fd13eb7e129f850340d6af
BLAKE2b-256 checksum
How to use checksums
db51b65652b90bd32711ba0c54ef6b0e61c8f22639d4623b3e92092a5d8e7940
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp315-abi3.abi3t-manylinux_2_28_aarch64.whl
Size 817.4 kB
Tags CPython 3.15 Linux glibc 2.28+ ARM64 abi3 abi3t
SHA-256 checksum
How to use checksums
fb4924ae093d676688db559e68848fe8494cd2ceb257bf8ffea1e58b97c5b1a7
BLAKE2b-256 checksum
How to use checksums
8a14477f7919ff4fc276880bad5fecbedc77cbc20c720423d93ec4df3ec35dfa
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp315-abi3.abi3t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 840.6 kB
Tags CPython 3.15 Linux glibc 2.17+ x86-64 abi3 abi3t
SHA-256 checksum
How to use checksums
a33704088bad3b8e2fd18f53c4c3b2d7643cdaa2c1fb7409726806f1efde3658
BLAKE2b-256 checksum
How to use checksums
cd0fca96ff8e6b9da419b682c1c403648e6fa4a2ef735d44383a086543add234
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp315-abi3.abi3t-macosx_11_0_arm64.whl
Size 792.8 kB
Tags CPython 3.15 abi3 abi3t macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
6353f064f32bd7f5229c44cbd7cbbc38f0191e26a1d93acf509d8316fe90b569
BLAKE2b-256 checksum
How to use checksums
04619024893dc0b395b121554ffac51fffc3eb0d7d07d7ad5ae4238f90944a92
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp315-abi3.abi3t-macosx_10_12_x86_64.whl
Size 822.8 kB
Tags CPython 3.15 abi3 abi3t macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
cf2e0a03bfe845c97ff0472f02b33f236a11e87023fb7cc00ad3b90d1809dff7
BLAKE2b-256 checksum
How to use checksums
cead58cc68e6aaf1a4a09994ee0cfd4fead0eb018295c4e24a7e849165c4814f
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp314-cp314-win_amd64.whl
Size 749.9 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
4c34d86b825cf148ba8a9f0b65dd7df9ae91252e03a56f7a644a4add157f7978
BLAKE2b-256 checksum
How to use checksums
1ed6d2a2f36e0326904e9cae38fe3952fd2013cd631d059f1f8026f2be88ca7d
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp314-cp314-manylinux_2_28_aarch64.whl
Size 822.3 kB
Tags CPython 3.14 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
eb55eb26bb0087f2ec26388ce6ff154f8c889f94fe842d51d9c4c62e553fc3ab
BLAKE2b-256 checksum
How to use checksums
ae94bbb9dd70151d54a64638b887400db50c996d1b90cc0b608d33a1c1b1ed01
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 845.8 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
05e9dd8930a57346e09bcb6a450bf8b54e7c6266fcd1413e4a412fde032b9d7f
BLAKE2b-256 checksum
How to use checksums
cca4e22baf371d09f515b0ad120c08329af85b526faf69e2f58565202559130c
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp314-cp314-macosx_11_0_arm64.whl
Size 803.1 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
0ee4e18b90cff1bec5f73499e0362ac83877ae83ae9c090ffbc587a143175a09
BLAKE2b-256 checksum
How to use checksums
75d2efd87153cf0461fedfff71ae58ce6f2530027dddbd9216cc436ee06f220c
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp314-cp314-macosx_10_12_x86_64.whl
Size 835.8 kB
Tags CPython 3.14 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
1432d96eec18f64d754410fcdba2640b6e9ac6d9c62e8b218fc98496f2f7c68f
BLAKE2b-256 checksum
How to use checksums
f055826463682b8138d0471570975df73ed0953333c75125daa83aea3a511743
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp313-cp313-win_amd64.whl
Size 752.9 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
b9ba9faa5097a6f55b3acdd4438f0c38e7c7f007393a7ec919f80cdc6b8a39c4
BLAKE2b-256 checksum
How to use checksums
21d25b22545f8fc931512fa711b9818c1c58618439ab5caf9e7e0d8b13451061
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp313-cp313-manylinux_2_28_aarch64.whl
Size 823.2 kB
Tags CPython 3.13 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
0674d01ea99f58dbbca21882364b089bb05b7b82c448479cbacba8e3b40379d2
BLAKE2b-256 checksum
How to use checksums
83a402361b141b217fa9905a044dffca7bf85847cefb47b0051ee1712d05c38d
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 846.9 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
2ca83ca98d1949dbf9a113be246253c0b95f5a7e9d497123a7b8a58082276cf8
BLAKE2b-256 checksum
How to use checksums
051eaca66fd06cc53160bc74735ed8837cd64fb61fe7f88160dbbfd12560dc6f
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp313-cp313-macosx_11_0_arm64.whl
Size 803.2 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
50762b21432cb40f39a948c7e16da396d4df95ae8aee20b9fb58fe87afcca959
BLAKE2b-256 checksum
How to use checksums
478372b7b8416ba1a3372bcd394b0d803940473316b36878b256d72fb55798de
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp313-cp313-macosx_10_12_x86_64.whl
Size 835.6 kB
Tags CPython 3.13 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
661c6eb427d0bbad3da8945171dc953bc02ce5de50ef88a85d9efa72c3d83840
BLAKE2b-256 checksum
How to use checksums
7bc5ebadfcdf651aa2bab014a6e12979308f5265aaa5ec2984f068b9b598a50e
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp312-cp312-win_amd64.whl
Size 752.2 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
4f94e4ececad2d06c1def1ca59504b82ef5ce1b854cbbff6d64db4f1c7f8e132
BLAKE2b-256 checksum
How to use checksums
aa15c7409abc85f45572d380867afbffd4d93a3fb3e8388251668bad294fa3ef
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp312-cp312-manylinux_2_28_aarch64.whl
Size 822.8 kB
Tags CPython 3.12 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
7fac41ce310136e1eadcd5adf211a66574fcb9bcdb0668cdf625fffcd357a5d8
BLAKE2b-256 checksum
How to use checksums
54add87d8e50bcd92ae6d06979b20c4ab0af11da59b2e6a501d86462dad04165
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 846.3 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
44650fd76660fb4f6c5cf491712047f05ba6b49b5d64382b21a29e77208f425a
BLAKE2b-256 checksum
How to use checksums
64eb7b7176f6dd23da0a03e9e279f35f9060ac1b6e770643d312934158facf97
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp312-cp312-macosx_11_0_arm64.whl
Size 802.6 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
eda343364a0b10eae8868d07499954cad8b7d2e9b67b6bad1b573b93ca6da4eb
BLAKE2b-256 checksum
How to use checksums
5299dc3285c2c53fab21fb564b7d735c133fd0378f5448551ce56f5411847c0a
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp312-cp312-macosx_10_12_x86_64.whl
Size 835.0 kB
Tags CPython 3.12 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
7fb31162901d40045faf0821e4179327f1af029ffa04d11456b9cc38a98621d6
BLAKE2b-256 checksum
How to use checksums
f5a206211f6cab8729a83387c1a46c79daf895e5ce09b263c8d5d420c06a46a7
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp311-cp311-win_amd64.whl
Size 753.2 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
d9c8652dc747bf245199fa3b0f6f849e88a6e5eb8e482f515312ca8ab49c9771
BLAKE2b-256 checksum
How to use checksums
f8a7198e12265f66c762f52db2af37161473be963195c0c3144d0fa164ba58db
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp311-cp311-manylinux_2_28_aarch64.whl
Size 825.5 kB
Tags CPython 3.11 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
7ee84d2b517717eec0149cb3cd14b579b544366f6425a6b60d4c178f02a3064b
BLAKE2b-256 checksum
How to use checksums
1b306f5f67f8d5df7825ce924247701ccb5b5a53916274d2bf844092bd8c51df
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 847.1 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
cee4e23a15fca85ea04e754d675f65340427112be05afd48bcaf0c760f4d1f3e
BLAKE2b-256 checksum
How to use checksums
78f7d21c9fe0376afffa50380695680a7893de2b6888e957c761d7929d2a8985
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp311-cp311-macosx_11_0_arm64.whl
Size 805.0 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
c7534daca7c82ee3cd1c24f37d00d5e710cb531314c5923e2c34f1610e44759d
BLAKE2b-256 checksum
How to use checksums
c84ece1ef2de8c0fea571c5270c81862892a95b954cf012428c58531b58af946
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 10, 2026.

Transparency log

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

Download URL cachekit-0.26.0-cp311-cp311-macosx_10_12_x86_64.whl
Size 828.1 kB
Tags CPython 3.11 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
e208500571824a466521c7d2e257d83ca27442b54ead295d0d39ab7bdb02c5f2
BLAKE2b-256 checksum
How to use checksums
ed1351d530ff60d975995233e331a28170008745b398ab0194e75f448fb554dc
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 10, 2026.

Transparency log

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

Select from 26 files

Attestation for cachekit-0.26.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 10, 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.26.0 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