falsealpha
A C++ engine that searches thousands of formulaic trading signals, then tells you which of its own discoveries are fake.
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
trial clusters: ~709 independent bets -> luck bar +1.56 /yr (reported; the gate counts every formula)
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
trial clusters: ~667 independent bets -> luck bar +1.55 /yr (reported; the gate counts every formula)
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, even counting only the trial clusters as independent bets (0 of 30 runs had a finalist reach a train DSR of 0.95 either way). 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
trial clusters: ~1197 independent bets -> luck bar +1.64 /yr (reported; the gate counts every formula)
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. Many of those tries are near-copies of each other; grouping them (|corr| > 0.7) leaves about 1,197 independent bets, a luck bar of +1.64, and a Deflated Sharpe of 0.80: still a fail, so the verdict does not rest on the conservative count. 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.
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
- 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.
- Ledger. Every distinct formula the search scores is written to
ledger.csv.gz(formulas are canonicalised, soa + bandb + acount once). This is the N in the multiple-testing correction, not just the winners. Each formula is also assigned to a trial cluster: it joins the first cluster whose leader's train returns it matches with |corr| > 0.7, or leads a new one. The number of clusters estimates how many independent bets the search made. - 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.
- Holdout. The search and validation never receive the holdout days: the panel is physically truncated before they run.
falsealpha unsealscores 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 run reports how much by also deflating against the trial clusters (n_effective, dsr_effective, the "DSR vs clusters" column in the report), and the gate keeps the conservative count. 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_linearby recurrence. - Exact second moments.
ts_std,ts_zscore,ts_corrandts_covare 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 evalshows 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.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| falsealpha-0.2.0.tar.gz | 504.8 kB | With provenance | Details for falsealpha-0.2.0.tar.gz |
Built distributions (wheels)
Total release size: 6.4 MB
Release files / falsealpha-0.2.0.tar.gz
| Download URL | falsealpha-0.2.0.tar.gz |
|---|---|
| Size | 504.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3cadb8fc2dab25dff22a90c80243bfa2b6dfa44e41053b89d438e41635825063
|
|
BLAKE2b-256 checksum How to use checksums |
03af49402f07a77e1a221954e6a70fdedf9f406a4c61b8a33b464ea41355852d
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp315-cp315-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | falsealpha-0.2.0-cp315-cp315-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 287.2 kB |
| Tags | CPython 3.15 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
e57999ba281a882f96f5c04939892a16a9a451587a92087ef2af9cfd959a69aa
|
|
BLAKE2b-256 checksum How to use checksums |
9e022b6d2cad83a56f6b37cdce332fef52f05e8ec9601a1b27a6deb82fc26b8e
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp315-cp315-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | falsealpha-0.2.0-cp315-cp315-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 255.6 kB |
| Tags | CPython 3.15 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
7edd85ddd5cc5da1629caa13a0c2ba1ce072d4ea0eca9a4fb50047a922d850c8
|
|
BLAKE2b-256 checksum How to use checksums |
bf316cbbbee15cbc80f246b1f8fd0af2fd27b55ca7e9129c3b7678440529067b
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp315-cp315-macosx_11_0_x86_64.whl
| Download URL | falsealpha-0.2.0-cp315-cp315-macosx_11_0_x86_64.whl |
|---|---|
| Size | 231.1 kB |
| Tags | CPython 3.15 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
a1753469e944a2f6a40307bbdae7f51284c2f2192fe9185fe38dea819ab4c7e3
|
|
BLAKE2b-256 checksum How to use checksums |
04ede4e5514cc4b68923737def652bdfb2fadc4700bfcddda0c8becbc1bc9668
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp315-cp315-macosx_11_0_arm64.whl
| Download URL | falsealpha-0.2.0-cp315-cp315-macosx_11_0_arm64.whl |
|---|---|
| Size | 215.5 kB |
| Tags | CPython 3.15 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f60a92d3d1ff9ffe98ec95307c8fcfdda457812b6021f2b6dfae956a69a03e91
|
|
BLAKE2b-256 checksum How to use checksums |
0f6ce2f839e8f21d1757691cde785490d36c506be1e0bc9d5da071ebd19056ec
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | falsealpha-0.2.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 287.2 kB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
a80c2f1e2df0dc926c81cc4056ff0e5681d05eb0ac1c6f8b6d0add1985d86761
|
|
BLAKE2b-256 checksum How to use checksums |
165fbfc94fa291514066173b415f83e5eb871b66453747b48bb069be1012aac7
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | falsealpha-0.2.0-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 255.6 kB |
| Tags | CPython 3.14 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
7268b75101a8a9f9e539cacade2d49223e67d00b1966e077f2900eccdc6d4662
|
|
BLAKE2b-256 checksum How to use checksums |
b019999fcc955b4dd8ae6c43eefd85f8e51a34027f138659d17c1ad23e6388c8
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp314-cp314-macosx_11_0_x86_64.whl
| Download URL | falsealpha-0.2.0-cp314-cp314-macosx_11_0_x86_64.whl |
|---|---|
| Size | 231.1 kB |
| Tags | CPython 3.14 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
13f1cf5baf8e08e6555602c74a81d4940f2119fceb2cc52d2fa259bbf072bee4
|
|
BLAKE2b-256 checksum How to use checksums |
7cc8db1f62c63cb584e3239f0d7553879527dcd0c105cf8ad956c6ff1176a8fb
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | falsealpha-0.2.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 215.5 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
5b0edfaabb330fda5d1d41fbcee547503c8fa0c29cb5acdbc38161815f632960
|
|
BLAKE2b-256 checksum How to use checksums |
440cba8d2e6463c097f3c53c031bcebc237a04d3d9aac9afa35e40f4017faf0a
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | falsealpha-0.2.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 287.1 kB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
ea71587060b6b5a2b46d3e519f7f54de7a60bc62e2d2928b51651cda48cc662c
|
|
BLAKE2b-256 checksum How to use checksums |
3734b5d3e4a40b78c52a25c31e600dff85b3e0fd59942a07948e35698e521525
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | falsealpha-0.2.0-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 255.2 kB |
| Tags | CPython 3.13 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
8190162a82f30e8aaae61817fc3d37d865c7ebe59bec7713e69e61d9c8872e8a
|
|
BLAKE2b-256 checksum How to use checksums |
e432f16ef7356a8381e6fca878ec87f37207b439dc5e950e42c2b83c9edcde92
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp313-cp313-macosx_11_0_x86_64.whl
| Download URL | falsealpha-0.2.0-cp313-cp313-macosx_11_0_x86_64.whl |
|---|---|
| Size | 230.9 kB |
| Tags | CPython 3.13 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
a5fc10f789feee0fb4bd06284fac0311482a7d52317a2af763940472c05c1d0b
|
|
BLAKE2b-256 checksum How to use checksums |
1fd973d4bae005ed7a1ce923e8ae9ee382574d182d38b1854dcc143b8c05e8b2
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | falsealpha-0.2.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 215.0 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
166d9f67148903bcc9f3071706b6e0e2ad27beda5d71fc57e9c591b9efa3d287
|
|
BLAKE2b-256 checksum How to use checksums |
48117cfd281acd04de21eb619d8d6b909344884165f2200040740470ae934d4b
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | falsealpha-0.2.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 287.1 kB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
f236efa28d2d703c3f5fc014f08c03b12489bbcc8a091eeab8b67411228fe3e4
|
|
BLAKE2b-256 checksum How to use checksums |
3e92ee83e4314de65d83fdb6725b11963b68edc05d16c5ebdf68dcbf10d641eb
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | falsealpha-0.2.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 255.2 kB |
| Tags | CPython 3.12 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
c394f8b1ed0c08927c2a2d1056545ba0a8aa19b921733653a94cf6b038f83a18
|
|
BLAKE2b-256 checksum How to use checksums |
2a71b769de5ea67333f6f42f2a4976a0be2f18f0a15e25b821b664f7997c61b3
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp312-cp312-macosx_11_0_x86_64.whl
| Download URL | falsealpha-0.2.0-cp312-cp312-macosx_11_0_x86_64.whl |
|---|---|
| Size | 230.8 kB |
| Tags | CPython 3.12 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
1c535ff0d6dbbab70da668d1ff8ae4cda73b5da0e6d295b1910e8d7754ea6cfd
|
|
BLAKE2b-256 checksum How to use checksums |
53fbec4cbe3a1781d2dbfa91932696fa636f5613b08d9fe53e967e20735f2442
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | falsealpha-0.2.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 214.9 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
e620f281d90c3ee054a5c914419f1a5f4937591bfbb6e10cbeba033bc9fb2cbf
|
|
BLAKE2b-256 checksum How to use checksums |
2b77138dff5e5efcb3b7a37c47327ad426c9ccfe4cd699f1afffdc7b17795b16
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | falsealpha-0.2.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 285.7 kB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
ab46672747518585bb3cc3ecf3e27248fcc161061721bcfd52ad9d0f23410258
|
|
BLAKE2b-256 checksum How to use checksums |
192c04d87b141b30735a5d48435e99a1b899a654d63eb4d1482371dcad2b62bf
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | falsealpha-0.2.0-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 254.1 kB |
| Tags | CPython 3.11 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
a3981f27f9160a5acb5673be99f7bb45451df3872a065e6fe2086eb56d761f0a
|
|
BLAKE2b-256 checksum How to use checksums |
75345fa84c560b445f46c052a95b9ee1583c5e593695b604b9c4dc828baa4e8e
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp311-cp311-macosx_11_0_x86_64.whl
| Download URL | falsealpha-0.2.0-cp311-cp311-macosx_11_0_x86_64.whl |
|---|---|
| Size | 227.9 kB |
| Tags | CPython 3.11 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
6bee6cb006d7282f3ecf907c8a3d4fef636eff199f6773029d785d110945ad30
|
|
BLAKE2b-256 checksum How to use checksums |
e1f3931d2d147a652717de97d547c50698808d852aeeae50a52b5cd9891c2ced
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | falsealpha-0.2.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 212.7 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
eff72710860d64087c5af3e28729ddd18616caaa14cc7870695587e8e64e7e75
|
|
BLAKE2b-256 checksum How to use checksums |
d21aa2e4ccab92c1cc263df08f0d08ae89060b39637428dcc4bfdcbf3229966d
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | falsealpha-0.2.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 285.1 kB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
17abc08198f13fa4393dc864863c2acec1b89c3a3f8e13094ef63d34126abe22
|
|
BLAKE2b-256 checksum How to use checksums |
635944f24f09a9330e2ae7b8fb235052a4adb3639eb8b43155a4598884436eb2
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | falsealpha-0.2.0-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 253.0 kB |
| Tags | CPython 3.10 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
45698c523cb0ee78a1db90df5cbe71e00e3435b38fb089f079224b10063c5e18
|
|
BLAKE2b-256 checksum How to use checksums |
f65819ab009da2ab0d66425d99de9e0f2f1842e02eeacd96778e48396b180fb5
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp310-cp310-macosx_11_0_x86_64.whl
| Download URL | falsealpha-0.2.0-cp310-cp310-macosx_11_0_x86_64.whl |
|---|---|
| Size | 226.6 kB |
| Tags | CPython 3.10 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
4f94980f9463bd104fcb924d1b4f41532352a0cf6596284817092999874637f2
|
|
BLAKE2b-256 checksum How to use checksums |
53cccc4cee1e7e0f9e04b591f29027f21e5f107bb29fe87e924800e0dba74091
|
| 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 15, 2026.
Transparency logRelease files / falsealpha-0.2.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | falsealpha-0.2.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 210.7 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
729570f845dcfb9dcd05203b6b4b536999a85480a9b160aaf95a08a376ca3410
|
|
BLAKE2b-256 checksum How to use checksums |
7cd28a65e0c90142a8c02d69d7e8aededf4d21e72b2a5477b44cddab3dcaacf5
|
| 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 15, 2026.
Transparency logSecurity for falsealpha 0.2.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.
Attestation for falsealpha-0.2.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 15, 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.