Skip to main content

qvalid

Takes a trade log. Decides whether its numbers survive correction for search, sampling error, serial dependence and regime. Writes a report that names every test it could not run.

uv run python examples/validate_full.py

One command, no network, no configuration. It reads two files from tests/fixtures and writes examples/output/report.{html,json,tex}.

What it decides, and on what basis

A Sharpe ratio computed from a trade log is almost always reported without the three things that determine whether it means anything: how many configurations were tried before this one, how wide the sampling interval around it is, and whether the returns are serially dependent. qvalid computes the ratio and all three corrections, and refuses to state a verdict when any of them is missing.

Question Method
Is the Sharpe distinguishable from zero? Delta method interval, Mertens (2002), with Newey and West (1987) HAC
Does it survive the search that produced it? Deflated Sharpe and PBO, Bailey and Lopez de Prado (2014, 2017)
Is one strategy better than another? White (2000) Reality Check, Hansen (2005) SPA
How bad can the drawdown get? Stationary bootstrap, Politis and Romano (1994), against Magdon Ismail et al. (2004)
What is the chance of ruin? First passage with the Broadie, Glasserman and Kou (1997) continuity correction
Does the edge live in one regime? Causal labelling, Welch (1951) unequal variance test
Would it pass a proprietary desk? Barrier model over daily paths, rules declared in YAML

The example, verbatim

The sample log has 760 trades over 2.91 years. The report says:

Sharpe (sqrt q)              -0.91   interval [-2.58, 0.76]
observed max drawdown        0.154   quantile 0.68 of the simulated distribution
probability of ruin          0.211   at a barrier of 85,000
regime equality of means     p = 1.6e-11   over 9 states

deflated_sharpe   NOT_REQUESTED   the number of configurations tested was not declared
verdict           SUPPRESSED      required sections did not run

The interval contains zero, so the ratio is not distinguishable from zero. The regime test finds a real difference. And the verdict is suppressed, not negative: the run cannot say how many configurations were tried, so no correction for search was applied, and a strategy whose search correction did not run is not comparable with one whose did. Estimating that number would fabricate the input that determines the answer.

This is the design. An absent test is a typed state in the report, never a missing field and never a pass. No aggregate grade is produced, because collapsing heterogeneous evidence into one letter is the defect the tool exists to correct.

Install

pip install qvalid
qvalid validate trades.csv --config run.yaml --out report.html

Python 3.12 or newer. Importers for generic CSV, TradingView and NinjaTrader; a symbology map supplies contract multiplier and tick size, which the P&L coherence check needs.

Reproducibility

Two runs on the same input with the same seed, in one environment, produce byte identical reports with the timestamp excluded. That is the claim about the seed governing everything, and it is checked exactly.

Across environments the claim is weaker and measured rather than hoped for. Changing the version of numpy or scipy moves two of the report's 144 values by one or two units in the last place, because a third moment and an F survival function are reductions whose summation order those libraries choose. Every run of the test suite compares against the committed reference at 1e-9 relative, which is a thousand times tighter than the six significant figures the report renders, so the report a person reads is identical. Text is compared with no tolerance at all: a regime identifier or a suppression reason that changed is not a rounding difference.

Nothing inside core calls the BLAS, because the BLAS splits long reductions across threads and the summation order would then depend on how many cores the machine has.

Licence

MIT. Design notes, the mathematical specification and the decision log are in docs/, in Portuguese.

Metadata

Release files for qvalid 1.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for qvalid 1.0.1
File Size Uploaded Provenance Actions
qvalid-1.0.1.tar.gz 298.5 kB With provenance Details for qvalid-1.0.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for qvalid 1.0.1
File Interpreter ABI Platform Actions
qvalid-1.0.1-py3-none-any.whl Python 3 none any Details for qvalid-1.0.1-py3-none-any.whl

Total release size: 442.7 kB

Release files / qvalid-1.0.1.tar.gz

Download URL qvalid-1.0.1.tar.gz
Size 298.5 kB
Tags Source
SHA-256 checksum
How to use checksums
951a62e426e8b2470efb12db72baab508c147e45eece4c26aafcd4bdb9c0ea06
BLAKE2b-256 checksum
How to use checksums
34dc86a4c089dbd0743d23480bf3f08c43d8f869afd9f408342e7fc7e8d49495
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 Aug 5, 2026.

Transparency log

Release files / qvalid-1.0.1-py3-none-any.whl

Download URL qvalid-1.0.1-py3-none-any.whl
Size 144.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
71991af707d992106ae87170056c46ec4c62f3d3ac4923b1990431b6beca0b3f
BLAKE2b-256 checksum
How to use checksums
7fea4accbc223f1ed90d09159a6bc3eb7d75f86b1ec831e0faed81c17f0df3c5
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 Aug 5, 2026.

Transparency log

Security for qvalid 1.0.1

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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for qvalid-1.0.1.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 Aug 5, 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