cloture
End the multi-agent debate the millisecond the math proves who won — and catch when your judge panel is 2 correlated votes wearing 9 trench coats.
cloture is a zero-dependency Rust core (cloture-core) + single 2.47 MiB static CLI/MCP binary (cloture) + zero-dependency Python SDK (cloture) + C ABI (include/cloture.h) for sub-microsecond anytime-valid consensus stopping, correlated-panel auditing, sequential agent racing, active prediction-powered evaluation, poisoning-resistant fusion, and distributed <1 KB evidence monoids.
- Zero external Rust crates (
Cargo.lockis 15 lines;stdonly). - Zero Python runtime dependencies (
import cloturecold-starts in26.5 msvs253 msNumPy /860 msSciPy /2,131 msppi_py). - Exact finite-sample martingale & conformal guarantees — valid at every data-dependent stopping time, with zero p-hacking and zero asymptotic small-sample approximations.
- Built-in JSON-RPC 2.0 MCP server (
cloture mcp,76.7 µsmedian tool roundtrip) and one-command self-benchmark (cloture bench). - Battle-tested:
266 / 266tests passing (55Rust core +8Python/CLI/MCP integration +203independent adversarial statistical, FFI, and fuzzing breaker tests).
Why cloture?
Multi-agent systems and LLM evaluation pipelines bleed tokens, wall-clock latency, and statistical validity in five ways:
- Fixed-
Nself-consistency / Best-of-Nwastes 40%–92% of calls on easy prompts while under-sampling hard ones; naive early stopping ("stop when 5 agree" orp < 0.05peeking) inflates false-certification rates to 28.5%–53.8%. - LLM-as-a-judge panels suffer correlated error collapse: 9 frontier judges often deliver only ~2.2 effective independent votes, losing ~20 pp vs. the Condorcet independence prediction — and dropping redundant judges improves accuracy while cutting API cost.
- Correlated rollouts masquerade as population proof: pooling 16 correlated rollouts per prompt produces 33%–40% false-positive deployment certificates at nominal
5%error. - Fixed-horizon PPI (
ppi-python) and naive A/B racing break under continuous peeking (71%coverage under peeking;40%tie-null false positives for heuristic rankers) and have zero online defense against biased or adversarially inverted LLM judges. - Poisoned agents and doomed multi-turn trajectories corrupt naive ensembles and burn tokens long after success probability collapses.
cloture fixes all five in one sub-microsecond native engine.
10-Second Quickstart
Install
# Python SDK (universal py3-none wheel, zero runtime deps)
pip install cloture
# Single static CLI & MCP binary (SHA-256 verified)
curl -fsSL https://raw.githubusercontent.com/pgg898200-ship-it/cloture/main/scripts/install.sh | sh
# Rust CLI / crate (zero external crates)
cargo install cloture-cli
# Or build from source (~18s, zero dependencies)
cargo build --release --workspace && ./target/release/cloture bench
1. Stop parallel async LLM/agent rollouts the millisecond consensus is certified
import asyncio
import cloture
# Category-agnostic CITE: works over arbitrary strings, code patches, SQL, or JSON
result = await cloture.consensus(
spawn_fn=lambda i: call_agent_async(prompt, seed=i),
delta=0.05,
max_calls=32,
concurrency=8,
)
print(result.winner, f"certified in {result.n_samples}/32 calls (cancelled {result.n_cancelled} in-flight)")
# Grey-box ASC-D: pass LLM logprobs / softmax vectors for 40%–92% fewer trajectories
probs = cloture.extract_logprob_distribution(top_logprobs, ["A", "B", "C", "D"])
stopper = cloture.AscdStopper(k=4, delta=0.05, max_budget=64)
dec = stopper.update(probs)
2. Audit a correlated multi-agent / LLM-as-a-judge panel
import cloture
report = cloture.audit_panel(votes, gold, n_perms=2000, n_condorcet_sims=2000, n_boot=1000)
print(f"K={report.k_judges} judges -> {report.n_eff_kish:.2f} effective votes (95% CI [{report.n_eff_ci_low:.2f}, {report.n_eff_ci_high:.2f}])")
print(f"Condorcet gap: {report.condorcet_gap*100:.1f} pp | permutation p={report.permutation_p_value:.5f}")
3. Stream from stdin or attach as an MCP server
# Halt an open-ended vote stream the millisecond CITE certifies a winner
printf '42\n42\n42\n42\n42\n42\n42\n42\n42\n42\n' | ./target/release/cloture stop --mode cite --delta 0.05
# Grey-box ASC-D stopping on streamed probability vectors
printf '[0.9,0.05,0.05]\n[0.88,0.07,0.05]\n' | ./target/release/cloture stop --mode ascd --k 3 --delta 0.05
# Audit a judge panel JSON ({"votes": [[...]], "gold": [...]})
./target/release/cloture audit --file panel.json
# Run built-in Rust microbenchmarks on your CPU
./target/release/cloture bench
# Start zero-dependency JSON-RPC 2.0 MCP server over stdio (Claude Code / Cursor / Codex)
./target/release/cloture mcp
Verified Head-to-Head Benchmarks
All numbers below were measured live on Intel Xeon @ 2.30 GHz (2 vCPU), Python 3.12.16, Rust 1.100.0, against real PyPI packages (confseq==0.0.11, ppi-python==0.2.3, expectation==0.6.1, online-cp==0.4.0, bayesbench==0.4.0.dev0, numpy==1.26.4, scipy==1.15.3). Full raw receipts live in benchmarks/results.json; reproduce with PYTHONPATH=python .venv/bin/python benchmarks/run_benchmarks.py.
1. Multi-Agent Consensus Stopping (delta = 0.05, 200 trials/regime)
| Regime | cloture.AscdStopper (Grey-Box) |
cloture.CiteStopper (Unbounded) |
Fixed-64 / Fixed-256 | Naive Peeking (p < 0.05) |
|---|---|---|---|---|
Easy (K=4, gap 0.45) |
21.0 calls (100% acc, 67.2% saved vs 64, 91.8% vs 256) |
58.7 calls (100% acc) |
64 / 256 (100% acc) |
21.0 calls (100% acc) |
Medium (K=4, gap 0.25) |
38.7 calls (100% acc, 39.5% saved vs 64, 84.9% vs 256) |
141.0 calls (100% acc) |
64 (99.5%) / 256 (100%) |
46.1 calls (100% acc) |
Hard (K=4, gap 0.12) |
127.5 calls (100% acc, 50.2% saved vs 256; budget=64 lock: 55.4 calls, 99.0% acc) |
245.3 calls (98.5% acc) |
64 (86.5%) / 256 (98.5%) |
118.1 calls (96.0% acc) |
Exact-Tie Null (K=4, gap 0.00) |
0.0% false cert |
0.0% false cert |
— | 28.5% false cert (5.7x violation) |
Open-Ended Zipf (K=200, gap 0.30) |
— (requires known K) |
70.9 calls (100% acc, 72.3% saved vs 256) |
256 (100% acc) |
26.0 calls (100% acc) |
Open-Ended Tie Null (K=200) |
— | 0.5% false cert (<= 5%) |
— | 30.5% false cert (6.1x violation) |
CPU Latency (K=4 ASC-D) |
2.21 µs Py batch / 2.32 µs Rust (28.9x faster than NumPy 63.8 µs, 25/25 exact stop parity) |
247 ns Py batch / 271 ns Rust |
— | — |
2. Correlated-Panel Audit (K=9 judges, N=1,000 items, 2k perms + 2k Condorcet MC + 1k bootstrap)
| Metric | cloture.audit_panel |
Vectorized NumPy / SciPy Ref | Result |
|---|---|---|---|
| Median Wall-Clock | 317.7 ms |
1,539.7 ms |
4.8x faster (max_det_diff = 2.66e-15) |
Effective Votes (n_eff) |
2.21 Kish (95% CI [2.10, 2.34]) / 2.13 Eigen |
Identical (1.3e-15 diff) |
9 judges behave like 2.2 independent votes |
Condorcet Gap & Omnibus p |
+20.43 pp (94.91% null vs 74.48% actual), p = 0.0005 |
p = 0.0005 |
Correlated errors destroy majority lift |
| LOO Redundant-Judge Pruning | Drop 1 judge (#6): +1.52 pp acc, -11.1% cost; Drop 2 (#6,#8): +2.72 pp acc (74.5% -> 77.2%), -22.2% cost |
Identical | Fewer, less-correlated judges win |
3. Realized vs. Population Correlated Rollouts (rho = 0.60, 30 prompts x 16 rollouts, delta = 0.05)
| Method | Null False-Fire (theta = 0, 300 reps) |
Power (theta = +0.25, same 480-rollout budget) |
|---|---|---|
| Naive Pooled Z-test | 33.0% (broken) |
— |
| Naive Pooled Empirical-Bernstein CS | 40.0% (broken) |
— |
| Single-Unit Consensus Misfire | 17.3% prompt 0 (99.3% of reps have >=1 bad prompt) |
— |
cloture.PopulationCert |
0.7% (exact <= 5%; rho_hat = 0.60, ceiling 1.69) |
27.3% at 30x16 -> 88.0% at 120x4 (guided by optimal_rollouts) |
4. Anytime-Valid Confidence Sequences & Racing vs. Real PyPI Competitors (alpha = 0.05)
| Engine / Library | Anytime Miscoverage (500 x 1k, p=0.7) |
Width @200 / @1000 |
Throughput (ns/step) |
Notes |
|---|---|---|---|---|
cloture.EmpiricalBernsteinCS |
1.0% |
0.218 / 0.110 |
88.9 ns Rust / 110 ns Py batch / 5.16 µs Py stream |
O(1) memory, zero allocs |
cloture.BettingCS(G=201) |
3.6% |
0.190 / 0.095 (tightest) |
6.32 µs Py batch / 11.8 µs Py stream |
28.4x faster & tighter than confseq.hedged_cs |
confseq.predmix_empbern_cs (C++) |
1.0% |
0.222 / 0.112 |
442 ns batch-100k |
4.0x slower than cloture EB-CS batch |
confseq.hedged_cs(201) |
0.0% (30 trials) |
0.214 / 0.119 |
179,326 ns batch-1k |
28.4x slower than cloture.BettingCS |
expectation.EmpiricalBernsteinCS (Rust) |
0.0% (chunk-50) |
0.284 / 0.120 |
22.8 ns single-call final-only / 1,132,769 ns 1-step stream |
Single-call final-only is faster; 1-step streaming is 219x slower than cloture Py stream |
| Naive CLT / Wald Peeking | 53.8% (10.8x violation) |
0.127 / 0.057 |
83.6 ns |
Invalid under continuous monitoring |
Multi-Arm Racing (6 arms, 200 tasks, 1,200 Fixed-N evals):
cloture.AgentRace(paired=True):299.9evals (75.0%saved),100.0%accuracy,0.0%null FWER.cloture.AgentRace(paired=False)(LUCB):709.0evals (40.9%saved),100.0%accuracy,0.0%null FWER.- vs.
bayesbench: On a 6-arm 200-task race,cloture.AgentRace(paired=True)finishes in2.75 ms(306evals) vs.bayesbench.BayesianRanker30,514 ms(1,200evals,11,112xfaster). On exact-tie0.50 vs 0.50pairwise nulls (30 trials),bayesbench.comparefalse-certifies40.0%(196.6 ms/trial) vs.cloture.PairedEProcess0.0%(0.205 ms/trial,959xfaster).
5. Active-PPI++ vs. ppi-python, Human-Only CS, & Adversarial LLM Judges
| Scenario | cloture.ActivePPI |
ppi-python (Peeking every 200) |
ppi-python (Single Fixed Horizon) |
Human-Only EB-CS (10%) | Naive LLM Judge |
|---|---|---|---|---|---|
Accurate Biased Judge (r=0.92, +0.15 bias, N=4000, 10% audit) |
99.0% anytime cov, width 0.146, 6.29x var red, 1.46x eff mult, 0.98 ms batch |
71.0% cov (breaks under peeking!), 19.8 ms |
96.0% cov, width 0.054 (tighter iff no peeking), 1.03 ms |
99.0% anytime cov, width 0.177, 2.10 ms |
0.0% cov (+0.15 bias) |
Adversarially Inverted Judge (f = 1 - y, N=2000) |
99.0% anytime cov (lambda_hat = 0.0000) |
— | 94.0% fixed cov |
100.0% anytime cov |
0.0% cov |
6. SafeFuse Quarantine, AbortCascade, OnlineConformal vs. online-cp, & 712-Byte EvidenceSketch
SafeFuse(5agents,2poisoned att=200, 50 trials): quarantines both poisoned agents on100%of runs (median94steps),0.0%clean-null FWER (and<= 0.75%even under adversarial heavy-tailed20*Bern(0.05),Exp(1), and left-skewed{0, 1.05}nulls), reducing cumulative loss by-200.0vs. uniform averaging (and beating the oracle clean mean by-2.74). RustSafeFuse(K=5)::update:1.24 µs.AbortCascade(500cal /500test, 50 trials, target recall0.92): achieves92.6%mean test recall (vs. naive uncalibrated0.35threshold collapsing to66.1%) while saving38.2%of failed-episode compute (27.8%total compute). Calibration:2.79 msmedian.OnlineConformal(4-rate AgACI, abrupt shift att=1000, target90%):64.5 ns/stepRust /2.02 µsPython —2,930xfaster (Rust) /93.3xfaster (Python) thanonline-cpSimpleJumper(188.9 µs) and154xfaster thanonline-cpConformalRidgeRegressor(312.6 µs). Post-shift coverage recovers to94.4%vs.online-cpCRR68.0%and fixed unadapted33.5%.EvidenceSketch: fixed712-byte wire format (b"CLTR"+ FNV-1a 64-bit checksum),76.3 nsRust merge (852 nsPython ctypes),0.0exact diff across1,000-worker fleet merge (100,000obs) and exact Leave-One-Out subtraction.
Engines & Module Map
| Engine | Rust (cloture-core) |
Python (cloture) |
CLI / MCP | Mathematical Foundation |
|---|---|---|---|---|
| 1. Consensus Stopping | mode::{AscdStopper, CiteStopper, PopulationCert} |
AscdStopper, CiteStopper, PopulationCert, consensus(), consensus_dist() |
cloture stop, cloture_mode_stop, cloture_population_cert |
Grey-box ASC-D (2026), unbounded Kraft-IUT CITE (2026), deterministic budget lock, unit-level PopulationCert (Nov 2026) |
| 2. Correlated-Panel Audit | panel::{PanelAudit, OnlinePanelTracker} |
audit_panel(), OnlinePanelTracker |
cloture audit, cloture_audit_panel |
Kish & Jacobi Eigenvalue $n_{\text{eff}}$, stratified Condorcet null & permutation test, Krippendorff's $\alpha$, LOO pruning (May 2026) |
| 3. Anytime-Valid CS, Racing & Active-PPI++ | betting::*, race::{AgentRace, e_bh_discoveries}, ppi::ActivePPI |
EmpiricalBernsteinCS, BettingCS, PairedEProcess, AgentRace, race_agents(), e_bh_discoveries(), ActivePPI |
cloture race, cloture ppi, cloture_agent_race, cloture_active_ppi |
Predictable plug-in EB-CS & Hedged ONS Betting CS (JRSS-B 2024), LUCB + paired e-process racing, e-BH (2022), centered affine Active-PPI++ (2024–2026) |
| 4. Safe Fusion & Abort Cascades | fuse::SafeFuse, cascade::{AbortCascade, OnlineConformal} |
SafeFuse, AbortCascade, OnlineConformal |
cloture_safe_fuse |
Scale-Free BOA + unclamped Fan-inequality quarantine over max(LOO mean, LOO median), Conformal Risk Control (CRC), 4-rate AgACI |
| 5. Distributed Evidence Monoid | sketch::EvidenceSketch |
EvidenceSketch |
Rust / C / Python | Fixed 712-byte associative, commutative wire monoid with exact LOO subtraction |
Honest Scope Boundaries
- Single-shot fixed-horizon PPI without peeking: If you collect a single static dataset, look once at
N, and never monitor sequentially, asymptotic normalppi-pythonproduces tighter intervals (0.054vs.0.146) because it does not pay the finite-sample anytime-validO(log log t)and bounded-range Fan-inequality price. Usecloture.ActivePPIwhenever you stream, peek, stop early, or need worst-case finite-sample protection against biased/adversarial judges. - Single-call offline batch EB-CS: If you only want one final Empirical-Bernstein bound over an already-collected static array of 100k floats without intermediate checks,
expectationis faster in a single batch call (22.8 ns/stepvs.110 ns/step). For sequential/streaming monitoring (checking after every observation or mini-batch),clotureis219xfaster in Python andO(1)per step. - Population vs. unit certificates:
AscdStopperandCiteStoppercertify the modal answer of a single prompt's rollout distribution. To certify deployment-level superiority across prompts under correlated rollouts, always aggregate unit means inPopulationCert.
Documentation & Agent Discovery
- Drop-In Ecosystem Integrations (OpenAI/vLLM, Judge Panels, MCP, CI Gates, C FFI)
- Mathematical Architecture & Proofs
- Full 7-Suite Benchmark Report & Raw JSON Receipts
- Tool & Library Comparisons
- C ABI Header | MCP Registry Manifest | Changelog
- AI Agent Skill Instructions |
llms.txt|llms-full.txt
License
Metadata
Release files for cloture 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| cloture-0.1.0-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for cloture-0.1.0-py3-none-win_amd64.whl |
| cloture-0.1.0-py3-none-manylinux_2_28_x86_64.whl | Python 3 | none | Linux glibc 2.28+ x86-64 | Details for cloture-0.1.0-py3-none-manylinux_2_28_x86_64.whl |
| cloture-0.1.0-py3-none-manylinux_2_28_aarch64.whl | Python 3 | none | Linux glibc 2.28+ ARM64 | Details for cloture-0.1.0-py3-none-manylinux_2_28_aarch64.whl |
| cloture-0.1.0-py3-none-macosx_11_0_x86_64.whl | Python 3 | none | macOS 11.0+ x86-64 | Details for cloture-0.1.0-py3-none-macosx_11_0_x86_64.whl |
| cloture-0.1.0-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for cloture-0.1.0-py3-none-macosx_11_0_arm64.whl |
Total release size: 3.2 MB
Release files / cloture-0.1.0-py3-none-win_amd64.whl
| Download URL | cloture-0.1.0-py3-none-win_amd64.whl |
|---|---|
| Size | 214.0 kB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a2bb947b23c7818579cea1073eb3263f6d03c8776195be6112d6f87ad3b3c294
|
|
BLAKE2b-256 checksum How to use checksums |
8aad5a58e6c43a26061f0fe18bfc9cc4ff323d85deab540a8df8401213f7cfc6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logRelease files / cloture-0.1.0-py3-none-manylinux_2_28_x86_64.whl
| Download URL | cloture-0.1.0-py3-none-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
a9236ad235cdcb166148886343670458384460e8d7f61847e51c99f180f55aac
|
|
BLAKE2b-256 checksum How to use checksums |
811e9c1b43283656394f2659f56c7ca986341373605a3edb94fa5f283c8a1bef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logRelease files / cloture-0.1.0-py3-none-manylinux_2_28_aarch64.whl
| Download URL | cloture-0.1.0-py3-none-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Linux glibc 2.28+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
e954563f762793c64d943b099459923d79dece14b3e3ca0806639dd37ee6ee29
|
|
BLAKE2b-256 checksum How to use checksums |
5fbe3d99014eb501f21c08108a9d1dccdaf9510f4897fb56ce53b0155e57fa68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logRelease files / cloture-0.1.0-py3-none-macosx_11_0_x86_64.whl
| Download URL | cloture-0.1.0-py3-none-macosx_11_0_x86_64.whl |
|---|---|
| Size | 310.4 kB |
| Tags | Python 3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
301c388d51a6ee4ad6789713190e6a75ed30dcbf790c26f8518cba0f7cf3ee5a
|
|
BLAKE2b-256 checksum How to use checksums |
629cc539bb326150a71a0830e123ae275189dc1f1301f366bcacb005d540baa8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logRelease files / cloture-0.1.0-py3-none-macosx_11_0_arm64.whl
| Download URL | cloture-0.1.0-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 300.9 kB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1f1ea4c11c249d11fb5027a1d4a3c24fab0db81ce5fc5ec6c5e2adb1d63c6353
|
|
BLAKE2b-256 checksum How to use checksums |
cb999f9a9d9c007dd49107a049a260451c4ef61f80785622e79461c53af7e039
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logSecurity for cloture 0.1.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 5 files in this release have been uploaded with provenance metadata.
Attestation for cloture-0.1.0-py3-none-win_amd64.whl
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 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.