Automic VaultAutomic Vault

brew

Install verapdf with Homebrew, Nix

Open-source industry-supported PDF/A validation. Version 1.30.2 via Homebrew; verified 2026-06-03.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install verapdf

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#verapdf

nixpkgs package indexes · pkgs/by-name/ve/verapdf/package.nix · source: api.github.com

overview

Package summary

Open-source industry-supported PDF/A validation

Commands and aliases

  • verapdf
  • verapdf-gui

history

Project history and usage

veraPDF is an open-source, industry-supported validator for PDF/A and related PDF conformance work. It is used by archives, memory institutions, preservation workflows, vendors, and automated pipelines that need machine-readable evidence that PDF files conform to long-term preservation standards.

Project history

The veraPDF consortium was led by the Open Preservation Foundation and the PDF Association to produce a validator accepted by the PDF technology industry. The project grew out of the EU-funded PREFORMA procurement program, which pushed for open, transparent conformance checking for preservation file formats.

A first public prototype appeared in 2015 as a proof of concept rather than a complete validator. Version 1.0 was released in January 2017, validating all parts and conformance levels of ISO 19005 PDF/A and beginning the next PREFORMA testing and acceptance phase.

After PREFORMA funding ended in 2017, veraPDF moved into long-term stewardship by the Open Preservation Foundation, with Dual Lab providing active maintenance and user support. That maintenance model is a major part of the project's significance: PDF/A validation needs continuity because archives preserve documents for decades.

Adoption history

veraPDF became a reference tool in digital preservation because it addressed a gap: institutions needed an open validator whose rules could be inspected, discussed, and aligned with PDF Association technical working-group decisions. The Library of Congress and digital-preservation tool catalogs describe it as a tool and library for validating PDF/A against ISO 19005 parts and profiles.

Its audience includes memory institutions, digital repositories, vendors, and batch-processing workflows. Unlike GUI-only PDF tools, veraPDF's CLI and machine-readable reports make it usable in ingest pipelines, repository QA, and continuous validation jobs.

How it is used

The Homebrew package exposes `verapdf` for command-line validation and `verapdf-gui` for interactive use. CLI users run it over one or many PDFs, choose report formats such as XML, JSON, HTML, text, or raw output, and use flavor/profile options to select the conformance target.

Beyond PDF/A validation, veraPDF includes feature extraction and a policy checker. Institutions can express local policy checks over PDF features, which lets the tool support preservation QA decisions that go beyond a strict pass/fail reading of the PDF/A standard.

Why package nerds care

veraPDF is package-manager significant because it turns a standards and preservation problem into a reproducible local command. That is exactly what archivists, CI pipelines, and repository operators need when validation must be repeatable and auditable.

Timeline

  • 2014-2015: veraPDF is initiated through PREFORMA-backed open-source preservation work.
  • July 2015: The first public prototype is released.
  • January 2017: veraPDF 1.0 ships with coverage for PDF/A parts and conformance levels.
  • 2017 onward: OPF sustains and maintains the project after PREFORMA funding ends.
  • 2020s: veraPDF continues as part of OPF's reference toolset and expands maintenance releases for validation, policy checking, and CLI workflows.

Related projects

  • veraPDF is related to PDFBox Preflight, Adobe Acrobat Preflight, JHOVE, DROID, Siegfried, and other digital-preservation validation tools. Its distinctive role is open, industry-backed PDF/A validation tied closely to PDF standards work.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Installs with 1 runtime dependencies.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
<veraPDF-install-path>/config~/verapdf/config

executables

Installed executables

CommandKindExposureNote
verapdfcliglobal executable
verapdf-guicliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version1.30.2
manager updated2026-06-03
local dataok
upstreamcurrent
latest detectedv1.30.2

https://github.com/veraPDF/veraPDF-apps

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:verapdf
Version1.30.2
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/verapdf
Homepagehttps://verapdf.org/home/
Repositoryhttps://github.com/veraPDF/veraPDF-apps
Upstream docshttps://docs.verapdf.org/
LicenseGPL-3.0-or-later OR MPL-2.0
Source archivehttps://github.com/veraPDF/veraPDF-apps/archive/refs/tags/v1.30.2.tar.gz
Last updated2026-06-03T13:58:30Z
Pulseupdated
Dependenciesopenjdk
Build dependenciesmaven
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameverapdf
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

verapdf

nix profile install nixpkgs#verapdf
  • normalized package name match
  • Matched by: Verapdf
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ve/verapdf/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Nix92%

verapdf-gui

nix profile install nixpkgs#verapdf-gui
  • installed executable or alias match
  • Matched by: Verapdf Gui
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ve/verapdf-gui/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment