opake-auditing
Empirical privacy auditing for Opake: one-run estimator (Steinke et al. 2023), coin-flip canary partitioning, and loss-based membership-inference attacks.
Install
Install the root package as described in the repository installation guide.
Use its auditing extra to include this component.
opake-auditing depends on opake-engine and scipy; both install
automatically with the extra.
Quick start
import opake.auditing as auditing
from opake.random import key
cf = auditing.coin_flip(dataset, num_canaries=1000, key=key(42))
# ... DP-SGD training loop ...
estimate = auditing.one_run(scores, coin_flip=cf)
By default, canaries are sampled from the dataset's natural rows. Pass
candidate_indices= to restrict selection to a precommitted pool of constructed
or selected records.
Layout
opake.auditing.one_run— one-run estimator (Steinke et al. 2023)opake.auditing.coin_flip()— coin-flip canary partitioningopake.auditing.loss_scores()— loss-based membership inference viavmap
Metadata
Release files for opake-auditing 0.16.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opake_auditing-0.16.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / opake_auditing-0.16.1-py3-none-any.whl
| Download URL | opake_auditing-0.16.1-py3-none-any.whl |
|---|---|
| Size | 36.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2ca876851734771dab4ffc800ce86460dc8dde87d1107455973e191613e8a20
|
|
BLAKE2b-256 checksum How to use checksums |
be72f4b01f9af42502893bc94745d81a416567dad0027f1357d1f03e642d5e13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency log