Audit Proteomics Exchange (PRIDE) study metadata from the command line.
I made PXAudit because I was checking PRIDE submissions by hand and got tired of repeating the same steps.
PXAudit reads project metadata and file listings from the PRIDE Archive, classifies the deposited files, assigns a seven-level FAIR tier and a separate quantification-readiness tier, then saves the audit to SQLite. It does not download deposited data files.
Quick start
PXAudit supports Python 3.12 through 3.14. The source checkout uses uv:
git clone https://github.com/LangeLab/PXAudit.git
cd PXAudit
uv sync
uv run pxaudit check PXD000001
The first audit queries PRIDE and creates pxaudit_results.db in the current directory. API responses are cached under ~/.pxaudit_cache/, so a fresh repeat audit does not need another request.
PXAudit currently audits PRIDE PXD accessions. Safe identifiers from other ProteomeXchange repositories are accepted as Unverifiable; repository adapters are not implemented yet. The unreleased v0.6.0 package is PRIDE-only. Partner adapters are planned after publication.
Audit evidence uses the v3 outcomes passed, failed, and unknown. Unknown evidence is shown as ?, does not block tier progression, and is counted in ambiguity_count; export consumers should treat has_* columns as strings rather than integer booleans.
Interactive terminal output uses restrained color for flags and tiers when standard output is a TTY. Meaning stays in the glyphs and labels, so --no-color, NO_COLOR, quiet mode, and redirected output are plain by default. An explicit color = true setting is the opt-in override.
Common tasks
# Audit a list containing one accession per line
uv run pxaudit bulk-audit --input accessions.txt --format tsv --output results.tsv
# For large local runs, add --batch-size N to commit after each N accessions.
# Inspect the stored file inventory
uv run pxaudit manifest PXD000001
# Review effective settings and cache state
uv run pxaudit config show
uv run pxaudit cache info
# Review aggregate counts from a stored database
uv run pxaudit summary --db pxaudit_results.db
# Generate a self-contained HTML report
uv sync --extra report
uv run pxaudit report --db pxaudit_results.db --output report/
The default batch size is 1, preserving per-accession durability. A stop-on-error or interrupted run rolls back its active batch; --continue-on-error commits pending successes before skipping the failed accession.
Run uv run pxaudit --help or uv run pxaudit COMMAND --help for command-line help.
Use as a Python library
The public Python API provides the same single-accession audit used by the CLI and persists the completed result to SQLite:
from pxaudit import audit_accessions, check_accession
one = check_accession("PXD000001", db_path="audits.db")
print(one.tier, one.quant_tier)
cohort = audit_accessions(["PXD000001", "PXD004683"], db_path="audits.db")
print(len(cohort))
db_path may be a string or pathlib.Path. The helpers use the local JSON cache, normalize accessions, and stop on the first error. Use the CLI bulk-audit --continue-on-error command when a batch must continue after an individual failure. Lower-level callers can import compute_audit and FileClass for deterministic scoring and filename classification.
Documentation
The wiki contains the detailed contracts and examples:
- Home: workflow overview and report preview
- CLI Reference: commands, flags, configuration, caching, errors, and exit codes
- Tier System: FAIR and quantification tiers, evidence flags, and scoring rules
- Database Schema: tables, columns, migrations, and example queries
- FAQ: supported accessions, file classification, offline use, and common scoring questions
- Development: setup, architecture, testing, style, and CI
Contributions and issue reports are much appreciated. The development guide explains the local checks and documentation workflow.
Citation
If you use PXAudit in your research, please cite it as:
@software{ergin_pxaudit_2026,
author = {Ergin, Enes Kemal},
title = {{PXAudit}: A command-line tool for auditing {Proteomics Exchange} study metadata},
year = {2026},
version = {0.6.0},
url = {https://github.com/LangeLab/PXAudit},
license = {MIT},
}
A CITATION.cff file is included in the repository root for tools that parse it automatically (e.g. GitHub's Cite this repository button, Zenodo).
License
MIT License. See LICENSE for details.
Metadata
Release files for pxaudit 0.6.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 | |
|---|---|---|---|
| pxaudit-0.6.0.tar.gz | 56.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pxaudit-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 118.0 kB
Release files / pxaudit-0.6.0.tar.gz
| Download URL | pxaudit-0.6.0.tar.gz |
|---|---|
| Size | 56.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2986d408273e47057ba9ed6c89950039c8263a02f9da867a79f9b1746aefe239
|
|
BLAKE2b-256 checksum How to use checksums |
53d0e847213137e692f436c0a4a4809ff537e9f8a4669557c9d74b46257e8738
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 18, 2026.
Transparency logRelease files / pxaudit-0.6.0-py3-none-any.whl
| Download URL | pxaudit-0.6.0-py3-none-any.whl |
|---|---|
| Size | 61.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1bd8ccd58e4c65a122788c84508e62ce68ff7631d2f01d68f6957ed750d54c2f
|
|
BLAKE2b-256 checksum How to use checksums |
a2c87c7f67d2ecbd39a692a2042af33094825ca3cfdc1b118d6f131b3403b015
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 18, 2026.
Transparency log