Skip to main content

ReproFig

ReproFig makes a figure carry the exact comma-separated values (CSV), optional statistics, software version, source fingerprints, and reproduction instructions needed to audit it later. It works for general data figures; scientific figures and publication workflows are the main use case because their evidence and reporting requirements benefit most. The same reprofig/1 record works in SVG, PDF, PNG, JPEG, TIFF, WebP, AVIF/HEIF, PowerPoint, Word, Excel, HTML, HDF5, netCDF-4, FITS, and deterministic ZIP/RO-Crate bundles.

python -m pip install reprofig

ReproFig requires Python 3.10 or newer. The core has no required scientific stack. The main installation choices are:

python -m pip install reprofig           # ordinary save, embed, inspect, extract
python -m pip install "reprofig[excel]"  # publication workbooks
python -m pip install "reprofig[proof]"  # workbooks, statistics, visuals, signatures, encryption

Carrier-specific extras remain available for PDF, HEIF, HDF5, netCDF and FITS.

Create a master figure

from reprofig import save_figure

save_figure(
    figure,
    "Figure 1.pdf",
    data=dataframe,
    sources="analysis/source.csv",
    statistics=records,
    reproduction=True,
)

ReproFig infers the plotting package and version, captures the calling script, serializes the metadata, and computes all source, script, and table hashes. The user does not import JSON or write checksum code. Omit sources, statistics, or reproduction when they do not apply. This ordinary workflow does not activate proof checks, cryptography, interception, or extra dependencies.

A master embeds the exact CSV bytes used for the plot. This is the auditable source of truth and may contain private data or local paths, so do not upload it without checking it first. Sidecar files are optional and can be regenerated:

from reprofig import extract_artifact, publish_artifacts

extract_artifact("Figure 1.pdf", "Figure 1 extracted")
publish_artifacts(
    ["Figure 1.pdf", "Figure 2.jpg", "Slides.pptx"],
    output_dir="Publication",
    figure_profile="public",
    safe_columns=["condition", "value"],
)

Readable export names

Automatic exports use lowercase hyphenated names such as paired-change-record.json, paired-change-figure-data.csv, and paired-change-reproduced.svg. The permanent rf-... figure identifier stays inside the record and is added to a filename only when two readable names collide.

Pass export_name="paired-change" to extract_artifact, publish_artifacts, or reproduce_figure to override the automatic name. The fallback order is the explicit export name, original figure stem, current artifact stem, figure title, then figure. Existing automation can request the previous identifier and dotted-suffix names with naming="legacy"; the command-line equivalents are --name and --naming legacy.

Integrate another plotting package

Attach the plot meaning before its normal save step:

from reprofig import attach, save_figure

attach(
    figure,
    plotted_data=analysis_rows,
    statistics=statistical_records,
    analysis={"independent_unit": "participant"},
    column_classification={
        "condition": "safe",
        "value": "safe",
        "participant_id": "private",
    },
)
save_figure(
    figure,
    "Figure.png",
    producer={"package": "my-analysis", "package_version": "2.1.0"},
    render_preset="line_art",
)

New raster figures default to 300 dots per inch (DPI). Use screen for 150 DPI, continuous_tone for 300 DPI, line_art for 600 DPI, or pass an exact dpi, width, and height. Existing raster files are never resampled by embed_file; AVIF/HEIF metadata changes require allow_reencode=True because the available backend must rebuild those images.

Make publication-safe copies

The public profile retains only explicitly approved columns and source links. The minimal_public profile retains summary statistics and provenance without row-level data. Both are one-way derivatives of the master:

reprofig publish Figure.svg Figure.jpg --output-dir Submission \
  --profile minimal-public --safe-columns condition,value \
  --public-source dataset=https://repository.example/data.csv

The command-line interface also provides formats, inspect, validate, embed, extract, caption, scan, bundle, and fsb-export. Run reprofig formats to see optional dependencies and carrier capabilities.

Embedded metadata can be stripped by editors, social platforms, publisher pipelines, or format conversion. Keep the master. When the delivery route is unknown, send a .reprofig.zip bundle alongside the visible figure; its fixed layout and SHA-256 checksums make missing or changed files detectable.

Build a publication source-data workbook

Combine every unique embedded CSV with a normalized table of all plotted and unplotted tests:

from reprofig import build_publication_workbook

result = build_publication_workbook(
    "figures/",
    "Publication-source-data.xlsx",
    experiment_statistics="analysis/all-tests.json",
)

Set the ledger's coverage to analysis_complete only when it intentionally lists every analysis, including unplotted tests. That is a declaration, not proof that undisclosed analyses never occurred. See docs/publication_workbook.md.

Opt into proof-carrying output

from reprofig import bind_artist, save_figure, verify_proof

bind_artist(line, semantic_id="treated-series", columns=["time", "signal"])
save_figure(
    figure,
    "Figure-1.svg",
    plotted_data=rows,
    statistics=statistics,
    proof=True,
)
report = verify_proof(
    "Figure-1.svg",
    required=["internally_consistent", "display_verified"],
)

Complete figure reproduction is deliberately separate because it executes the embedded producer. It saves a second carrier and a report; later verification only reads those files and never reruns code:

from reprofig import reproduce_figure

run = reproduce_figure(
    "Figure-1.svg",
    bundle_root="figure-bundle",
    output_dir="figure-bundle/verification/reproduced",
    execute_trusted_producer=True,
)

This writes a readable carrier such as Figure-1-reproduced.svg; an explicit report_path remains available when a bundle requires a fixed internal report location.

Use statistics_reproduced when declared statistics match the same implementation, statistics_independently_verified when a separate reference implementation matches, and figure_reproduced only when a separately saved figure also matches. See docs/figure-reproduction.md.

Typed statistical specifications can additionally reconstruct declared source transformations and recalculate supported tests. A passing report proves that the stated evidence agrees with the output; it does not prove that source data are true or that the chosen method is scientifically appropriate.

Presentation-ready examples

examples/diverse-verification-workflows contains three standalone workflows rather than variations of one plot:

  • Matplotlib paired trajectories with a Wilcoxon signed-rank test;
  • Seaborn regression with an ordinary least-squares slope test;
  • Plotly box plots with raw observations and a one-way analysis of variance.

Each example has one master figure, one statistical result, a separately saved reproduction, unpacked evidence, and a browser-ready page placing the clean figure beside a PNG of its exact syntax-highlighted producer code. The code image also has an editable SVG and its own registered plot-that bundle.

Signatures answer “has this evidence changed since this key signed it?” Trust stores separately answer “do I accept that key for this purpose?” Individual tables, statistics, provenance, or specifications can be encrypted for a password or named X25519 recipient before signing. See docs/proof-carrying-verification.md and docs/security.md.

Develop and verify

python -m pip install --upgrade build twine
python -m build
python -m twine check dist/*

Report problems through the GitHub issue tracker. Please cite ReproFig using the metadata in CITATION.cff.

ReproFig is licensed under the BSD 3-Clause licence.

Release files for reprofig 0.5.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 reprofig 0.5.1
File Size Uploaded
reprofig-0.5.1.tar.gz 148.2 kB Details

Built distribution (wheel)

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

Total release size: 336.1 kB

Release files / reprofig-0.5.1.tar.gz

Download URL reprofig-0.5.1.tar.gz
Size 148.2 kB
Tags Source
SHA-256 checksum
How to use checksums
175427555fa48461b7d750f01fb382fa7110ff13fd239ea87786432b98fb2bf6
BLAKE2b-256 checksum
How to use checksums
cec862d90c1275a196ae72da4a2b9b68975914a4adb8ad056a4db10d501b2651
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 26, 2026.

Transparency log

Release files / reprofig-0.5.1-py3-none-any.whl

Download URL reprofig-0.5.1-py3-none-any.whl
Size 187.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1259558afc4901b80e54307528922749ef97329946299a98b739f2190ee1544e
BLAKE2b-256 checksum
How to use checksums
6a1136bcd75a2616b7ad5617d2795838c37e41208a483c44928022a2c43c48ba
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 26, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.5.1 This release

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

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