apud-bench
Can a vision-language model say where it read what it reports?
apud-bench evaluates vision-language models on historical handwritten documents with three
tasks:
| Task | Question | Metric |
|---|---|---|
| Transcription | Read a line, full page vs IIIF region crop | CER / WER |
| Grounding | Given a line of text, return its box on the page | IoU against ground-truth line geometry |
| Citation faithfulness | In a long transcription, is each line attributed to the right region? | correct / wrong / hallucinated citations |
Existing HTR benchmarks for VLMs score reading only. Document-grounding benchmarks use modern
PDFs. apud-bench brings grounding and citation to manuscripts, across scripts and centuries.
Status: pre-alpha. The subset registry is in place; loaders and evaluation are next.
Data
The benchmark is built from openly downloadable ground truth produced by the HTR community (HTR-United, Zenodo, GitHub). Nothing is redistributed: a build script fetches each subset from its original source, normalises its geometry and text, and generates static IIIF manifests and tiles locally.
- core: open licences only (CC-BY, CC-BY-SA, CC0, Apache-2.0, MIT, Etalab 2.0)
- nc-extension: NonCommercial subsets, kept separate
- hold: candidates whose licence or access still needs confirming
Every derived artefact carries the licence of the subset it comes from. See
DATA_LICENSES.md and subsets/subsets.yaml.
uv run apud-bench stats # registry summary
uv run apud-bench list --tier core
uv run apud-bench check # enforce licence/tier rules
Credits
All ground truth belongs to its creators; each subset entry links to its source. Please cite the original datasets alongside this benchmark.
License
Code: Apache-2.0. Data: per subset, see DATA_LICENSES.md.
Metadata
Release files for apud-bench 0.0.1
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 | |
|---|---|---|---|---|
| apud_bench-0.0.1.tar.gz | 22.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apud_bench-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.6 kB
Release files / apud_bench-0.0.1.tar.gz
| Download URL | apud_bench-0.0.1.tar.gz |
|---|---|
| Size | 22.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c5f3872649f522cc4aa8e02186e006143aa544c97f6c4bb2e54391cc16bfd75
|
|
BLAKE2b-256 checksum How to use checksums |
71be7916351cdd93352095c3c0868e7d524088d0caef3fe38bc4b3b37ce5d2aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 27, 2026.
Transparency logRelease files / apud_bench-0.0.1-py3-none-any.whl
| Download URL | apud_bench-0.0.1-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc5c2ec0e36a0108c821013dd6a2434c151ce47fdab6274ffef17244e5426cc0
|
|
BLAKE2b-256 checksum How to use checksums |
23edca7fdd567a98b5ebe5bc8d7120c7d8debfae630cc342271fe788443cd1a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 27, 2026.
Transparency logSecurity for apud-bench 0.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for apud_bench-0.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 Oct 27, 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.