Automic VaultAutomic Vault

brew

Installer verapdf avec Homebrew, Nix

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de verapdf pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install verapdf

local Homebrew formula metadata

Linux

Nixvérifié · 92%
nix profile install nixpkgs#verapdf

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

aperçu

Résumé du paquet

Open-source industry-supported PDF/A validation

Commandes et alias

  • verapdf
  • verapdf-gui

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

  • 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.

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

  • narrow executable package without higher-risk signals

Signaux

  • metadata:no-higher-risk-signals

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
  • S’installe avec 1 dépendances d’exécution.
  • Les métadonnées de compilation listent 1 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des 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

exécutables

Exécutables installés

CommandeTypeExpositionNote
verapdfcliexécutable global
verapdf-guicliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-08
version du gestionnaire1.30.2
gestionnaire mis à jour2026-06-03
données localesOK
amontà jour
dernière version détectéev1.30.2

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

  • OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:verapdf
Version1.30.2
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/verapdf
Page d'accueilhttps://verapdf.org/home/
Dépôthttps://github.com/veraPDF/veraPDF-apps
Docs amonthttps://docs.verapdf.org/
LicenceGPL-3.0-or-later OR MPL-2.0
Archive sourcehttps://github.com/veraPDF/veraPDF-apps/archive/refs/tags/v1.30.2.tar.gz
Dernière mise à jour2026-06-03T13:58:30Z
Pulseupdated
Dépendancesopenjdk
Dépendances de compilationmaven
Bouteilledisponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

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

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

verapdf

nix profile install nixpkgs#verapdf
  • normalized package name match
  • Correspondance par : 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
  • Correspondance par : 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

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • 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