Skip to main content

falsealpha

CI License: MIT

A C++ engine that searches thousands of formulaic trading signals, then tells you which of its own discoveries are fake.

falsealpha mining six years of Binance data

Search hard enough and you will always find a backtest that looks good. falsealpha does the search fast in C++20, records every formula it tried, and keeps a result only if it beats the luck it took to find it.

$ falsealpha data noise --out noise.npz          # 2,500 days x 60 assets of pure noise
$ falsealpha mine noise.npz runs/noise
6002 formulas tried -> 50 finalists -> 0 survivors
  luck bar (train): best of 6002 unskilled strategies ~ Sharpe +1.84 /yr
  Reality Check p 0.942 (gate)   SPA p 0.800
  PBO 0.95  (share of splits where the in-sample best finalist lands in the bottom half)

$ falsealpha data planted --out planted.npz      # same, plus one hidden alpha
$ falsealpha mine planted.npz runs/planted
6397 formulas tried -> 50 finalists -> 3 survivors
  luck bar (train): best of 6397 unskilled strategies ~ Sharpe +1.85 /yr
  Reality Check p 0.000 (gate)   SPA p 0.000
  PBO 0.00  (share of splits where the in-sample best finalist lands in the bottom half)
  [PASS] train +5.87 (DSR 1.00)  val +4.94 (DSR 1.00)  (decay_linear(ts_sum(volume, 3), 5) * ts_sum(volume, 5))
$ falsealpha unseal runs/planted
combined: holdout Sharpe +4.08 /yr, P(true Sharpe > 0) 1.00, 498 days

Across 30 independent noise panels (1,500 days × 60 assets, population 200 × 6 generations; scripts/noise_calibration.py), the firewall let through 0 formulas. The Reality Check gate never opened (0 of 30); the Deflated Sharpe alone would also have caught everything. Mean PBO was 0.49, a coin flip, which is what overfitting to noise looks like.

On real data: six years of crypto

The default search on every Binance USDT pair that was ever in the daily top 100 by dollar volume: 2,465 days × 570 assets, delisted coins included, 10 bps costs, trading one day after the signal.

$ falsealpha data binance --out data/binance-top100.npz
$ falsealpha mine data/binance-top100.npz runs/crypto        # 45 s on an M3 Pro
7376 formulas tried -> 50 finalists -> 0 survivors
  luck bar (train): best of 7376 unskilled strategies ~ Sharpe +1.88 /yr
  Reality Check p 0.475 (gate)   SPA p 0.185
  PBO 0.73  (share of splits where the in-sample best finalist lands in the bottom half)
  [fail] train +2.06 (DSR 0.64)  val -1.08 (DSR 0.00)  min(((quote_volume / ts_mean(ts_delta(open, 20), 5)) - high), -ts_sum(trades, 10))
  [fail] train +2.01 (DSR 0.60)  val -1.79 (DSR 0.00)  min(((ts_mean(ts_delta(open, 20), 3) * ts_sum(volume, 10)) - ts_cov((open * open), low, 10)), -ts_sum(trades, 10))
  [fail] train +1.86 (DSR 0.48)  val +1.02 (DSR 0.14)  ts_sum((-trades * ts_cov(close, quote_volume, 10)), 40)

The best formula the search found earns a Sharpe of +2.06 a year over four years of training data, after costs. Shown alone, that is a backtest people trade. The firewall rejects it on the training data already: 7,376 tries at nothing would be expected to produce about +1.88 by luck, so its Deflated Sharpe is only 0.64. On the next 16 months, which the search never saw, it loses money (−1.08 a year), and so does the runner-up (−1.79). The few finalists that stay positive out of sample (+1.02 at best) are well within what luck explains over 493 days (Reality Check p = 0.48), and PBO is 0.73: picking the in-sample best finalist usually picks a below-median one.

So the honest result of this run is no tradable alpha, and the holdout (May 2025 to September 2026) stays sealed for a better search. That is the tool working: it is built to say "no" when the evidence is not there.

Run report

How it works

 panel ──► train ──────────────► validation ──────────► holdout (sealed)
           GP search, every       finalists scored       opens once, after
           formula logged         on unseen days         you stop searching
              │                        │                       │
              ▼                        ▼                       ▼
        Deflated Sharpe vs     Deflated Sharpe vs        combined survivors:
        ALL trials             the finalists; Reality    Sharpe, P(Sharpe > 0);
                               Check gate; PBO           every look logged
  1. Search. Genetic programming over an Alpha101-style formula language: ramped half-and-half initialisation, subtree crossover, point / subtree / hoist mutation, tournament selection, a parsimony penalty, and a novelty penalty against a hall of fame so it keeps finding different signals rather than near-copies (|corr| ≤ 0.7 between finalists). Fitness is the net long-short Sharpe on the train period only.
  2. Ledger. Every distinct formula the search scores is written to ledger.csv.gz (formulas are canonicalised, so a + b and b + a count once). This is the N in the multiple-testing correction, not just the winners.
  3. Firewall. A finalist survives only if it passes all of:
    • Train Deflated Sharpe ≥ 0.95 (Bailey & López de Prado 2014): the train Sharpe must beat the expected maximum of N unskilled strategies, where N is the whole ledger.
    • Validation Sharpe > 0 with Deflated Sharpe ≥ 0.95, deflated for the number of finalists scored on the unseen validation days.
    • White's Reality Check, p < 0.05 (White 2000), a global gate on validation returns: is the best finalist better than flat once you allow for having looked at all of them? Stationary bootstrap (mean block 10, 1,000 draws). Hansen's SPA test (Hansen 2005), the studentised version with consistent recentring, is reported alongside but is not the gate: at this sample size its measured size is 8–9% at a nominal 5%, while the Reality Check holds 4.5–6% (scripts/snoop_size.py, 1,000 null simulations per setting).
    • PBO (Bailey, Borwein, López de Prado & Zhu 2017) is reported, computed over the finalists' train + validation returns: combinatorially symmetric cross-validation over 16 blocks (12,870 splits), the share where the in-sample best finalist lands in the bottom half out of sample.
  4. Holdout. The search and validation never receive the holdout days: the panel is physically truncated before they run. falsealpha unseal scores the survivors and their equal-risk combination on the holdout once; a second look needs --force, and the report shows every look.

One deliberate deviation from the DSR paper. The paper sets the luck bar from the variance of Sharpe ratios across trials. In a search that finds something real, dozens of variants of that signal inflate that variance and the test ends up punishing the discovery (on the planted data it rejects a true signal with a Sharpe of 9). falsealpha uses the null variance, 1/(T−1): the expected best of N strategies with no skill. Counting every distinct formula as a trial overstates the number of independent trials, so the bar is conservative. The paper's version is still computed and stored (sr0_train_paper).

Quick start

pip install falsealpha

falsealpha data planted --out planted.npz   # random data with one hidden alpha
falsealpha data noise   --out noise.npz     # random data, no alpha at all
falsealpha mine planted.npz runs/planted    # search + firewall + runs/planted/report.html
falsealpha unseal runs/planted              # look at the holdout, once

falsealpha data binance --out binance.npz   # every USDT pair, delisted included (~10 min download the first time)
falsealpha info binance.npz
falsealpha eval binance.npz "-rank(ts_delta(close, 5))"
falsealpha mine binance.npz runs/crypto

Each run writes config.json, ledger.csv.gz, finalists.json, nets.npy, holdout.json and a self-contained report.html (no network, light and dark mode).

Python

import falsealpha as fa
from falsealpha import run

panel = fa.Panel.load("binance.npz")
signal = fa.evaluate("rank(ts_corr(close, volume, 10))", panel.core())        # days x assets
bt = fa.backtest(signal, "returns", panel.core(), delay=1, cost_bps=10)       # daily IC, gross, cost, net
fa.summarize(bt, 0, 1000)                                                     # Sharpe, IC, IC IR, turnover

verdict = run.mine("binance.npz", "runs/x", run.MineConfig(population=400, generations=25))

The statistics are exposed on their own: fa.expected_max_sharpe, fa.probabilistic_sharpe, fa.pbo, fa.snoop_tests.

Formula language

Fields are whatever the panel holds; Binance panels have open high low close volume quote_volume vwap returns trades. Infix + - * / and unary minus work, as do numeric constants.

kind operators
elementwise neg abs log sign add sub mul div max min
cross-sectional (universe members, one day) rank zscore demean scale
time-series (trailing d days, today included) ts_delay ts_delta ts_sum ts_mean ts_std ts_zscore ts_min ts_max ts_argmin ts_argmax ts_rank decay_linear ts_corr ts_cov

NaN rules: a time-series window must be full of real data; cross-sectional ops only see universe members with a value; a variance below 1e-20 of the mean square counts as zero.

Backtest convention. Weights are the cross-sectional rank of the signal, demeaned and scaled to gross 1 (dollar-neutral). A signal built from data up to close t trades at close t+delay (default 1) and earns the next day's return. Costs are charged per unit of turnover. A member with no next-day return (delisted, gap) earns 0, i.e. it is sold at its last price.

The engine

  • Time-major panels. A T × N panel stores one contiguous row of assets per day, so time-series ops sweep rows with per-asset state (vectorised across assets) and cross-sectional ops work on one contiguous row.
  • O(1) rolling sums with a periodic rebuild so floating-point drift can't build up; van Herk / Gil-Werman sliding min/max; decay_linear by recurrence.
  • Exact second moments. ts_std, ts_zscore, ts_corr and ts_cov are computed two-pass over each window. Running-moment updates (sums of squares, even rolling Welford) lose relative precision when a quiet window follows a volatile history at a high price level; the test suite has the random walk that proves it.
  • Common subexpressions within a formula are computed once; only repeated subtrees are cached, so memory stays at about one panel per tree level.
  • Parallel over formulas, deterministic for a given seed regardless of thread count (on one platform: C++ standard libraries draw random numbers differently); the GIL is released.

Verified, not assumed:

  • every operator matches an independent, loop-per-window numpy reference to 1e-9 (relative), including NaN holes, universe masks, constant columns and 3,000-day random walks at a price level of 5,000,000;
  • a property test perturbs every input after day k and checks no operator's output on or before day k moves (no look-ahead, by construction);
  • the Deflated Sharpe reproduces the worked example in Bailey & López de Prado (2014) (SR₀ = 0.1132, DSR = 0.9004);
  • the Reality Check rejects at about its nominal 5% on noise (SPA over-rejects at this sample size, measured and documented above) and both have power on a real edge; PBO averages about 0.5 on noise and about 0 with a dominant strategy;
  • the search recovers a planted alpha, the firewall passes it and rejects pure noise;
  • C++ tests run under AddressSanitizer and UBSan in CI.

Speed

Apple M3 Pro (11 cores), 2,000 days × 500 assets, best of 3:

time vs pandas
12 Alpha101-style formulas, falsealpha, 1 thread 501 ms 6.6× faster
same, 11 threads 131 ms 25× faster
same, pandas 3,307 ms
operator (1 thread) falsealpha pandas
rank(close) 29.7 ms 37.0 ms 1.2×
ts_mean(close, 20) 1.9 ms 11.5 ms 6×
ts_std(close, 20) 8.8 ms 19.1 ms 2×
ts_corr(close, volume, 20) 20.2 ms 77.6 ms 4×
ts_max(close, 20) 3.3 ms 21.0 ms 6×
ts_argmax(close, 20) 28.0 ms 774 ms 28×
ts_rank(close, 20) 10.3 ms 1,076 ms 104×
decay_linear(close, 20) 3.6 ms 520 ms 145×

The honest reading: on operators pandas implements in C (rank, rolling mean/std/corr) the gain is 1–6×, and ts_std / ts_corr deliberately pay for an exact two-pass computation. The large gains are on window operators pandas can only do through Python-level rolling().apply(). In a search, the parallelism is over formulas, so throughput scales with cores: the default noise run above scored 6,002 formulas over 2,500 days × 60 assets in about 5 seconds.

falsealpha bench reproduces this. The pandas side evaluates the identical formula text (canonical formulas are valid Python expressions) with the usual pandas idioms: rolling(), rank(axis=1, pct=True), rolling().apply() where pandas has no built-in. Where the definitions coincide the two agree to 1e-8 (tested). Most of falsealpha's single-thread time is rank, a sort per day, which pandas also does in compiled code; the big gaps come from window operators pandas can only do through Python-level apply.

Data

Crypto (built in). Binance's public dump (data.binance.vision) keeps every spot pair's daily candles, including pairs that were delisted, which is what makes a survivorship-free universe possible. The loader:

  • drops stablecoins, fiat pairs and leveraged tokens;
  • splits a ticker into separate assets when it goes more than 7 days without candles (LUNAUSDT resumes 18 days after the May 2022 collapse as a different coin);
  • handles the switch from millisecond to microsecond timestamps in 2025;
  • builds the universe each day from data up to that day: the top N by trailing 30-day dollar volume, with at least 60 days of history;
  • starts the panel in 2020 by default: before that Binance had fewer than 40 liquid USDT pairs on a typical day, too few for cross-sectional ranks (earlier data still counts as history).

US equities (planned). Free daily data with delisted names is scarce. The plan is point-in-time S&P 500 membership (fja05680/sp500) plus Tiingo's free tier, which carries delisted tickers, with results reported three ways (survivors only, point-in-time, and a delisting-loss stress) so the remaining bias is visible. yfinance can't be used: it has no delisted tickers and returns a different company for reused ones.

Limitations

  • Daily bars only; costs are a flat charge per unit of turnover, with no market impact or borrow costs.
  • A delisted asset is assumed sold at its last close. Real exits can be worse.
  • The holdout seal is an honour system with an audit trail (the look log and a fingerprint of the panel file), not cryptography.
  • Counting distinct formulas as trials is conservative; clustering trials into independent groups would give a sharper luck bar.
  • falsealpha eval shows validation results for any formula you type, and those looks are not counted. Hand-testing ideas on validation is a search the firewall cannot see; keep it to train, or count it yourself.

Development

python -m venv .venv && .venv/bin/pip install scikit-build-core pybind11 numpy pandas pytest certifi
.venv/bin/pip install --no-build-isolation -e ".[dev]"
.venv/bin/pytest                                                   # Python suite
cmake -S . -B build -DFALSEALPHA_BUILD_TESTS=ON && cmake --build build -j && ./build/core_tests

References

  • D. H. Bailey, M. López de Prado (2014). The Deflated Sharpe Ratio: Correcting for Selection Bias, Backtest Overfitting and Non-Normality. Journal of Portfolio Management 40(5).
  • D. H. Bailey, J. Borwein, M. López de Prado, Q. J. Zhu (2017). The Probability of Backtest Overfitting. Journal of Computational Finance 20(4).
  • P. R. Hansen (2005). A Test for Superior Predictive Ability. Journal of Business & Economic Statistics 23(4).
  • H. White (2000). A Reality Check for Data Snooping. Econometrica 68(5).
  • D. N. Politis, J. P. Romano (1994). The Stationary Bootstrap. JASA 89(428).
  • C. R. Harvey, Y. Liu, H. Zhu (2016). …and the Cross-Section of Expected Returns. Review of Financial Studies 29(1).
  • Z. Kakushadze (2016). 101 Formulaic Alphas. Wilmott 2016(84). arXiv:1601.00991

MIT licence.

Metadata

Release files for falsealpha 0.1.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 falsealpha 0.1.0
File Size Uploaded Provenance Actions
falsealpha-0.1.0.tar.gz 501.4 kB With provenance Details for falsealpha-0.1.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for falsealpha 0.1.0
File Actions
falsealpha-0.1.0-cp315-cp315-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.15 CPython 3.15 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for falsealpha-0.1.0-cp315-cp315-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
falsealpha-0.1.0-cp315-cp315-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.15 CPython 3.15 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for falsealpha-0.1.0-cp315-cp315-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
falsealpha-0.1.0-cp315-cp315-macosx_11_0_x86_64.whl CPython 3.15 CPython 3.15 macOS 11.0+ x86-64 Details for falsealpha-0.1.0-cp315-cp315-macosx_11_0_x86_64.whl
falsealpha-0.1.0-cp315-cp315-macosx_11_0_arm64.whl CPython 3.15 CPython 3.15 macOS 11.0+ ARM64 Details for falsealpha-0.1.0-cp315-cp315-macosx_11_0_arm64.whl
falsealpha-0.1.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for falsealpha-0.1.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
falsealpha-0.1.0-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for falsealpha-0.1.0-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
falsealpha-0.1.0-cp314-cp314-macosx_11_0_x86_64.whl CPython 3.14 CPython 3.14 macOS 11.0+ x86-64 Details for falsealpha-0.1.0-cp314-cp314-macosx_11_0_x86_64.whl
falsealpha-0.1.0-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for falsealpha-0.1.0-cp314-cp314-macosx_11_0_arm64.whl
falsealpha-0.1.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for falsealpha-0.1.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
falsealpha-0.1.0-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for falsealpha-0.1.0-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
falsealpha-0.1.0-cp313-cp313-macosx_11_0_x86_64.whl CPython 3.13 CPython 3.13 macOS 11.0+ x86-64 Details for falsealpha-0.1.0-cp313-cp313-macosx_11_0_x86_64.whl
falsealpha-0.1.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for falsealpha-0.1.0-cp313-cp313-macosx_11_0_arm64.whl
falsealpha-0.1.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for falsealpha-0.1.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
falsealpha-0.1.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.26+ ARM64, Linux glibc 2.28+ ARM64 Details for falsealpha-0.1.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
falsealpha-0.1.0-cp312-cp312-macosx_11_0_x86_64.whl CPython 3.12 CPython 3.12 macOS 11.0+ x86-64 Details for falsealpha-0.1.0-cp312-cp312-macosx_11_0_x86_64.whl
falsealpha-0.1.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for falsealpha-0.1.0-cp312-cp312-macosx_11_0_arm64.whl
falsealpha-0.1.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for falsealpha-0.1.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
falsealpha-0.1.0-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for falsealpha-0.1.0-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
falsealpha-0.1.0-cp311-cp311-macosx_11_0_x86_64.whl CPython 3.11 CPython 3.11 macOS 11.0+ x86-64 Details for falsealpha-0.1.0-cp311-cp311-macosx_11_0_x86_64.whl
falsealpha-0.1.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for falsealpha-0.1.0-cp311-cp311-macosx_11_0_arm64.whl
falsealpha-0.1.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for falsealpha-0.1.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
falsealpha-0.1.0-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for falsealpha-0.1.0-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
falsealpha-0.1.0-cp310-cp310-macosx_11_0_x86_64.whl CPython 3.10 CPython 3.10 macOS 11.0+ x86-64 Details for falsealpha-0.1.0-cp310-cp310-macosx_11_0_x86_64.whl
falsealpha-0.1.0-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for falsealpha-0.1.0-cp310-cp310-macosx_11_0_arm64.whl

Total release size: 6.3 MB

Release files / falsealpha-0.1.0.tar.gz

Download URL falsealpha-0.1.0.tar.gz
Size 501.4 kB
Tags Source
SHA-256 checksum
How to use checksums
b3ef9a18b49cd0bbc896b0e203899d0be11cb4425853019e9e9815abe9873f5d
BLAKE2b-256 checksum
How to use checksums
9e3d48666b91890ceb72b0304e4acec1f301d3a30998f10a2ae9a1e37388fe4b
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp315-cp315-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL falsealpha-0.1.0-cp315-cp315-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 283.8 kB
Tags CPython 3.15 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
6b2f24ea8b5023d43d74057ca2743f5b5702aa04b9e0dd440bb846684bac9786
BLAKE2b-256 checksum
How to use checksums
02afd5b3576eff8e2ca320e0979dc1d85f64d77460fe3319d0dc7bf53f9b611e
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp315-cp315-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL falsealpha-0.1.0-cp315-cp315-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 251.8 kB
Tags CPython 3.15 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
716d746520541a09d304da6becb40d4a525932f4d0080b3b11b1e392a22206d1
BLAKE2b-256 checksum
How to use checksums
3116b4a6aa938c86ca8a3d358259f1786949d42aaf559f683b79fa058d257a8e
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp315-cp315-macosx_11_0_x86_64.whl

Download URL falsealpha-0.1.0-cp315-cp315-macosx_11_0_x86_64.whl
Size 227.8 kB
Tags CPython 3.15 macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
4d6a98a725b6d3418835c81b5e3d9f60af72b8f166d79763db1ebcbc2cb60b5b
BLAKE2b-256 checksum
How to use checksums
74062b57bc582594d8f7bd942047e4ec2f1e8fa51c03509f2b390b81be6dca77
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp315-cp315-macosx_11_0_arm64.whl

Download URL falsealpha-0.1.0-cp315-cp315-macosx_11_0_arm64.whl
Size 212.2 kB
Tags CPython 3.15 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3e10abdfd1e84d26ad23a1a0e603464c51df925b644ea6465bf5d91892ad7b68
BLAKE2b-256 checksum
How to use checksums
3e9ab45f88beee14b2db2d8a0a7ecc20f5242e92d1f1526385279470ec2e041b
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL falsealpha-0.1.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 283.8 kB
Tags CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
b1b85572b49375179336e8cdd2c54131fed398e44ac597bbfec11baf8b2d1c22
BLAKE2b-256 checksum
How to use checksums
1ab27af979ebd007169d82ff55b27edadd003f1b0899b8d1fc9618f231c6bbc7
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL falsealpha-0.1.0-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 251.8 kB
Tags CPython 3.14 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
95a8066263c91b7d5294593a19a45289d90d0eb4faeb46e3afac30435b27052c
BLAKE2b-256 checksum
How to use checksums
2dad018c13f28feb3e8da5eeb7b6871280f7d33aaa39788232460b9ee1ae423c
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp314-cp314-macosx_11_0_x86_64.whl

Download URL falsealpha-0.1.0-cp314-cp314-macosx_11_0_x86_64.whl
Size 227.8 kB
Tags CPython 3.14 macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
e52278bf7021ba6d04f62930ca1a2fd654204a03b96c92ba2eaff96e60a904f8
BLAKE2b-256 checksum
How to use checksums
d35d39cd8b1a2f667f029786efd4d49d5d56937b37e891ecade3e06204a3b29e
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp314-cp314-macosx_11_0_arm64.whl

Download URL falsealpha-0.1.0-cp314-cp314-macosx_11_0_arm64.whl
Size 212.2 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
67efad06d67dbad2e7fb6cbc245f2e111a8cbc1056c4957dfde530c0011f53f2
BLAKE2b-256 checksum
How to use checksums
ef475b17f5ff7385b7e5a8130d874db257ee750edf184d447787b864ae16e2c7
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL falsealpha-0.1.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 283.5 kB
Tags CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
b78ae7863ccfaf042179778b4ad72ee7e17511a6aceb2807e248383122722ce7
BLAKE2b-256 checksum
How to use checksums
d94d4ab6e25edb04400971fb794bab2672f9420dd0a0ebc36f44b8a1648a83bd
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL falsealpha-0.1.0-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 251.4 kB
Tags CPython 3.13 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
91b4a7e4f3c5bdd2d817121bceed9a11cb49ab507ab80791de2d9bae6848b710
BLAKE2b-256 checksum
How to use checksums
3ec055cb9f0a5ee216de32f36b62b2d7716e483f2a63fe80caf0e34c483e78a4
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp313-cp313-macosx_11_0_x86_64.whl

Download URL falsealpha-0.1.0-cp313-cp313-macosx_11_0_x86_64.whl
Size 227.6 kB
Tags CPython 3.13 macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
573b5714b787059abdee331e5c7e09f5bd790effde23ab5a519a0f4ff51e55d1
BLAKE2b-256 checksum
How to use checksums
bd8e2e7253a27a598eeaffb1c902cc86f465da5dd5c17016c3e5f12f7a307c19
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL falsealpha-0.1.0-cp313-cp313-macosx_11_0_arm64.whl
Size 211.8 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
2c4dafe3fbbe7a6e5c5de7af6e5506f91bbbe0cfaa8f188716a430e48ade5c2f
BLAKE2b-256 checksum
How to use checksums
c7352185ec0baf85267ee2bd859f5c50207027fbb54ee300f23eb48f8d0e2ba2
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL falsealpha-0.1.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 283.5 kB
Tags CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
cce389a3926413522cad613f3c65a7b69dd72c7c3d9a6e3d80945b7432924e85
BLAKE2b-256 checksum
How to use checksums
97ac602472c3a3cda3d2b86c3d851d04496ebfbb4be6e868dfc602007d77f1f9
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL falsealpha-0.1.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 251.4 kB
Tags CPython 3.12 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
158e50a5dd3632122c361f35fa395a511f2bd848e60024c2b5d22bb543a39f01
BLAKE2b-256 checksum
How to use checksums
a48fbbccbf1e186f8a7d7b567aca787de8032af9f2fbd7e6eb101283f25b275f
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp312-cp312-macosx_11_0_x86_64.whl

Download URL falsealpha-0.1.0-cp312-cp312-macosx_11_0_x86_64.whl
Size 227.6 kB
Tags CPython 3.12 macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
78a3026370b6798927dbe95af6132d5f22bbb22097e69340602b86060cd0f923
BLAKE2b-256 checksum
How to use checksums
9ad5a13f0a67de039dff2ba3fc945c32bc9b7b9ce10903d89cc35f3529afd62a
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL falsealpha-0.1.0-cp312-cp312-macosx_11_0_arm64.whl
Size 211.8 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
80cf650b03ec9b2f3abaff9eea85c11000bd1e075d6910188966b5e70dc6d5de
BLAKE2b-256 checksum
How to use checksums
1f598551ba60f83e8a3fc581962d3a3f40b1798fd9b69e1eceec871832eadcbb
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL falsealpha-0.1.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 282.4 kB
Tags CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
5915c74165fda87eff5349d36ad2789557165bc21a093309d5c8e605e22048ad
BLAKE2b-256 checksum
How to use checksums
84ad7f44913c8aafd1b5579024265e2d9b6d393700c1a9ca781a548aae8e0cca
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL falsealpha-0.1.0-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 250.1 kB
Tags CPython 3.11 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
d990ec0e247aeadb6dab1bebcb12a428b05bcca2ef96e4049cdcab418a03d58d
BLAKE2b-256 checksum
How to use checksums
62a58b15502a807608c25ab0581bafc6408dda43b8d4b7a44647e561ec8c417d
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp311-cp311-macosx_11_0_x86_64.whl

Download URL falsealpha-0.1.0-cp311-cp311-macosx_11_0_x86_64.whl
Size 224.7 kB
Tags CPython 3.11 macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
edb1f662598a1207f7955471d0481f6c29fd8c14ae91a21e01fe346136602c0f
BLAKE2b-256 checksum
How to use checksums
58c987c4642100800c6e2425606eb08c848c92005b55b5b1ef1722247099c439
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL falsealpha-0.1.0-cp311-cp311-macosx_11_0_arm64.whl
Size 209.5 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
fe3e557e76dee599d920590422135056192f567de64e09975d95e8c022838f9c
BLAKE2b-256 checksum
How to use checksums
9fe1e7e8142a1e0455382b1bd655617003cb657f30aacde31de41fd34b61e9cd
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL falsealpha-0.1.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 281.7 kB
Tags CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
2a236e43012f70718ba77defdb518f457401bb447e813250d6f22dcb0207dd65
BLAKE2b-256 checksum
How to use checksums
6ac0947c0d2dd48420eaebc5905bdffb3b7b4d71945f6deac358604ddf38d7d5
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL falsealpha-0.1.0-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 249.1 kB
Tags CPython 3.10 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
fb9f48b50651e6f7258e08a4feb9928a23cd0fd15e3725e6244a4d78fb74062b
BLAKE2b-256 checksum
How to use checksums
73139e17046bcc29174b3eb77ddd8dc3d1df710ccab7f30dde91203434b87ed3
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp310-cp310-macosx_11_0_x86_64.whl

Download URL falsealpha-0.1.0-cp310-cp310-macosx_11_0_x86_64.whl
Size 223.2 kB
Tags CPython 3.10 macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
cb936c58b3e646dbe253a5fc2bac53652042dcac36e02062625ab1106db0253f
BLAKE2b-256 checksum
How to use checksums
600f48051911926d79b3bf31e3b1b7ebbc05a2091a6347b729631c4dba5b24a3
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 12, 2026.

Transparency log

Release files / falsealpha-0.1.0-cp310-cp310-macosx_11_0_arm64.whl

Download URL falsealpha-0.1.0-cp310-cp310-macosx_11_0_arm64.whl
Size 207.8 kB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
edd88e014fe76ec9389237c36192d647bdab829d03180658005870c63c9281ae
BLAKE2b-256 checksum
How to use checksums
f2af5fea7b459e2f5133a171982379f11649017e636246fb2a63c9306a026937
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 12, 2026.

Transparency log

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

Select from 25 files

Attestation for falsealpha-0.1.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 Oct 12, 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.

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